On Wed, 2016-12-14 at 11:54 +0100, Andreas Schwab wrote:
> This crashes the compiler on ia64.
Sorry about the breakage.
I'm able to reproduce this under valgrind on x86_64 (looks like a read
after free); I'm working on a fix.
Thanks
Dave
> FAIL: c-c++-common/raw-string-6.c -Wc++-compat (test
On Wed, Dec 14, 2016 at 11:54:21AM +0100, Andreas Schwab wrote:
> This crashes the compiler on ia64.
>
> FAIL: c-c++-common/raw-string-6.c -Wc++-compat (test for excess errors)
> Excess errors:
> /usr/local/gcc/gcc-20161214/gcc/testsuite/c-c++-common/raw-string-6.c:5:1:
> internal compiler erro
This crashes the compiler on ia64.
FAIL: c-c++-common/raw-string-6.c -Wc++-compat (test for excess errors)
Excess errors:
/usr/local/gcc/gcc-20161214/gcc/testsuite/c-c++-common/raw-string-6.c:5:1:
internal compiler error: Segmentation fault
0x4108571f crash_signal
../../gcc/topl
PR preprocessor/78680 identifies a crash when attempting to issue
a -Wformat warning, where the format string includes a string token
split across multiple physical source lines via backslash-continued
lines.
The issue is that libcpp is generating bogus range information for
such tokens.
For exam
