[Bug c++/102642] [11/12 Regression] ICE in get, at cgraph.h:2776 since r12-4032-g701075864ac4d1c6

cnsun at uwaterloo dot ca gcc-bugzilla@gcc.gnu.org
Fri Oct 15 02:53:48 GMT 2021


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102642

Chengnian Sun <cnsun at uwaterloo dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cnsun at uwaterloo dot ca

--- Comment #4 from Chengnian Sun <cnsun at uwaterloo dot ca> ---
The following might be a duplicate.

$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/scratch/software/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/configure
--enable-languages=c,c++,lto --enable-checking-yes --enable-multiarch
--prefix=/scratch/software/gcc-trunk --disable-bootstrap
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.0.0 20211014 (experimental) [master -gee9fa8a57] (GCC)

$ cat mutant.c
static a __attribute__((weakref("")));
static b __attribute__((weakref("")));
static b __attribute__((weakref("test4_f")));
test4_f;
c() { return b }

$ gcc-trunk -w mutant.c
mutant.c: In function ‘c’:
mutant.c:5:15: error: expected ‘;’ before ‘}’ token
    5 | c() { return b }
      |               ^~
      |               ;
At top level:
cc1: internal compiler error: in get, at cgraph.h:2776
0x836e01 varpool_node::get(tree_node const*)
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/cgraph.h:2776
0x836e01 varpool_node::analyze()
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/varpool.c:534
0xae7026 analyze_functions
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/cgraphunit.c:1288
0xae7fc1 symbol_table::finalize_compilation_unit()
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/cgraphunit.c:2508
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.


More information about the Gcc-bugs mailing list