[Bug preprocessor/69869] New: internal compiler error: Segmentation fault in call to skip_macro_block_comment when using '-traditional-cpp'
geir at cray dot com
gcc-bugzilla@gcc.gnu.org
Thu Feb 18 22:15:00 GMT 2016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69869
Bug ID: 69869
Summary: internal compiler error: Segmentation fault in call to
skip_macro_block_comment when using '-traditional-cpp'
Product: gcc
Version: 5.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: geir at cray dot com
Target Milestone: ---
The following test case fails in all versions of GCC I tried (4.7.3 through
5.3,0)
$ gcc --version
gcc (GCC) 5.3.0 20151204 (Cray Inc.)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ cat test.c
#define Concat2(a,b)a/**/b
all:
$(RM) Concat2(./bin/,*)
$ gcc -E -traditional-cpp test.c >/dev/null
test.c:1:0: internal compiler error: Segmentation fault
#define Concat2(a,b)a/**/b
^
0xa1c58f crash_signal
../../cray-gcc-5.3.0/gcc/toplev.c:383
0x1002b30 skip_macro_block_comment
../../cray-gcc-5.3.0/libcpp/traditional.c:129
0x1002b30 copy_comment
../../cray-gcc-5.3.0/libcpp/traditional.c:161
0x100336e _cpp_scan_out_logical_line
../../cray-gcc-5.3.0/libcpp/traditional.c:489
0x1003fcb _cpp_read_logical_line_trad
../../cray-gcc-5.3.0/libcpp/traditional.c:310
0x6bbe77 scan_translation_unit_trad
../../cray-gcc-5.3.0/gcc/c-family/c-ppoutput.c:326
0x6bbe77 preprocess_file(cpp_reader*)
../../cray-gcc-5.3.0/gcc/c-family/c-ppoutput.c:108
0x6ba6f0 c_common_init()
../../cray-gcc-5.3.0/gcc/c-family/c-opts.c:1033
0x62e9cc lang_dependent_init
../../cray-gcc-5.3.0/gcc/toplev.c:1836
0x62e9cc do_compile
../../cray-gcc-5.3.0/gcc/toplev.c:2053
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
$
More information about the Gcc-bugs
mailing list