On Tue, Nov 24, 2015 at 11:50:21AM +, Jay Foad wrote:
> I see now that it's already reported as PR c/68473.
Ooops, sorry, I knew about that one, but thought that's a different problem.
Marek
On 24 November 2015 at 11:34, Marek Polacek wrote:
> On Tue, Nov 24, 2015 at 11:24:38AM +, Jay Foad wrote:
>> r230331 also seems to be causing this on x86_64-pc-linux-gnu:
>>
>> $ cat x.c
>> #define P(b) b&&4
>> int a[]=0;
>> int f() { X||P(d); }
>> $ ~/gcc/build/gcc/cc1 -quiet -Wall x.c
>> [.
On Tue, Nov 24, 2015 at 11:24:38AM +, Jay Foad wrote:
> r230331 also seems to be causing this on x86_64-pc-linux-gnu:
>
> $ cat x.c
> #define P(b) b&&4
> int a[]=0;
> int f() { X||P(d); }
> $ ~/gcc/build/gcc/cc1 -quiet -Wall x.c
> [...]
> x.c:3:1: internal compiler error: in contains_point, at
