linux-kernel - Re: arm: kprobe compilation error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 09 Feb 2015 12:00:27 +0100
From:	Janusz Użycki <j.uzycki@...roma.com.pl>
To:	"Jon Medhurst (Tixy)" <tixy@...aro.org>
CC:	Russell King <linux@....linux.org.uk>,
	"David A. Long" <dave.long@...aro.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Wang Nan <wangnan0@...wei.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: arm: kprobe compilation error


W dniu 2015-02-09 o 10:44, Jon Medhurst (Tixy) pisze:
> Hi Janusz
>
> On Thu, 2015-02-05 at 16:17 +0100, Janusz Użycki wrote:
>> I got the compilation error on next-20150204:
>>
> [...]
>> In file included from arch/arm/probes/kprobes/core.c:37:
>> arch/arm/probes/kprobes/core.h:43: error: '[*]' not allowed in other
>> than a declaration
> [...]
>> gcc version 4.2.4
> Thanks for reporting this, is it OK if I add to a patch to fix this a
> line saying "Reported-by: Janusz Użycki <j.uzycki@...roma.com.pl>"?

sure

>
> Whilst the extra '*' looks like an obvious typo, it's interesting that
> your error message implies that it's allowed in some situations and that
> the version of GCC that I use (4.9.1) doesn't complain about it.
> If it's valid C, I've no idea what that syntax that might represent.
>
I've not find such extension in C11 but likely gcc's team knows the answer.
It also compiles using gcc 4.8.3. However I thing more people use older 
compilers
for different platforms.

best regards
Janusz

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/