public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/99447] New: [11 Regression] ICE (segfault) in lookup_page_table_entry
Date: Sun, 07 Mar 2021 10:35:45 +0000	[thread overview]
Message-ID: <bug-99447-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99447
           Summary: [11 Regression] ICE (segfault) in
                    lookup_page_table_entry
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: doko at debian dot org
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

seen with trunk 20210306 on x86_64-linux-gnu building the guymager package with
LTO.

$ g++ -Wl,-z,relro -ggdb -rdynamic -Wl,-flto -Wl,-z,relro -Wl,-O3 -o guymager
compileinfo.o aaff.o aewf.o config.o device.o dlgabort.o dlgacquire.o
dlgdirsel.o dlgautoexit.o dlgmessage.o dlgwait.o error.o fifo.o file.o hash.o
info.o infofield.o itemdelegate.o main.o mainwindow.o md5.o media.o qtutil.o
runstats.o sha1.o sha256.o table.o thread.o threadcompress.o threadhash.o
threadread.o threadscan.o threadwrite.o util.o moc_devicelistmodel.o
moc_dlgabort.o moc_dlgacquire.o moc_dlgautoexit.o moc_dlgacquire_private.o
moc_dlgdirsel.o moc_dlgdirsel_private.o moc_dlgmessage.o moc_dlgwait.o
moc_info.o moc_infofield.o moc_itemdelegate.o moc_main_private.o
moc_mainwindow.o moc_table.o moc_thread.o moc_threadcompress.o moc_threadhash.o
moc_threadread.o moc_threadscan.o moc_threadwrite.o   -lz -ldl -lguytools -lewf
-lbfio /usr/lib/x86_64-linux-gnu/libQt5Widgets.so
/usr/lib/x86_64-linux-gnu/libQt5Gui.so /usr/lib/x86_64-linux-gnu/libQt5DBus.so
/usr/lib/x86_64-linux-gnu/libQt5Core.so -lGL -lpthread
device.cpp: In member function ‘GetErrorText’:
device.cpp:155:1: internal compiler error: Segmentation fault
  155 | }
      | ^
0xc52c79 crash_signal
        ../../src/gcc/toplev.c:327
0x7f3b6994fd5f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x11ac4fb lookup_page_table_entry
        ../../src/gcc/ggc-page.c:630
0x11ac4fb ggc_set_mark(void const*)
        ../../src/gcc/ggc-page.c:1544
0x13bdefd gt_ggc_mx_basic_block_def(void*)
        /build/gcc-11-7yDrbQ/gcc-11-11-20210306/build/gcc/gtype-desc.c:1527
0x13bc981 gt_ggc_mx_gimple(void*)
        /build/gcc-11-7yDrbQ/gcc-11-11-20210306/build/gcc/gtype-desc.c:1238
0x11b188e gt_ggc_mx_cgraph_edge(void*)
        /build/gcc-11-7yDrbQ/gcc-11-11-20210306/build/gcc/gtype-desc.c:1403
0x11b15e1 gt_ggc_mx_symtab_node(void*)
        /build/gcc-11-7yDrbQ/gcc-11-11-20210306/build/gcc/gtype-desc.c:1349
0x11a903a gt_ggc_mx_lang_tree_node(void*)
        ./gtype-lto.h:284
0x11a904e gt_ggc_mx_lang_tree_node(void*)
        ./gtype-lto.h:280
0x11a9cde gt_ggc_mx_rtx_def(void*)
        /build/gcc-11-7yDrbQ/gcc-11-11-20210306/build/gcc/gtype-desc.c:722
0x11b435e void gt_ggc_mx<dw_attr_struct>(vec<dw_attr_struct, va_gc, vl_embed>*)
        ../../src/gcc/vec.h:1353
0x11b435e gt_ggc_mx_vec_dw_attr_node_va_gc_(void*)
        ./gt-dwarf2out.h:275
0x11b435e gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:45
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:27
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:47
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:27
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:47
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:27
0x11b4433 gt_ggc_mx_die_struct(void*)
        ./gt-dwarf2out.h:47
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

             reply	other threads:[~2021-03-07 10:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 10:35 doko at debian dot org [this message]
2021-03-07 10:41 ` [Bug lto/99447] " doko at debian dot org
2021-03-07 11:17 ` pinskia at gcc dot gnu.org
2021-03-08  8:46 ` marxin at gcc dot gnu.org
2021-03-08  9:01 ` rguenth at gcc dot gnu.org
2021-03-08 10:57 ` doko at debian dot org
2021-03-17 12:18 ` rguenth at gcc dot gnu.org
2021-03-17 12:20 ` rguenth at gcc dot gnu.org
2021-03-17 12:33 ` rguenth at gcc dot gnu.org
2021-03-17 12:38 ` rguenth at gcc dot gnu.org
2021-03-17 12:39 ` rguenth at gcc dot gnu.org
2021-03-17 13:30 ` hubicka at ucw dot cz
2021-03-25 15:27 ` marxin at gcc dot gnu.org
2021-03-26 11:03 ` doko at gcc dot gnu.org
2021-03-26 11:18 ` [Bug ipa/99447] " rguenth at gcc dot gnu.org
2021-03-29 18:20 ` hubicka at gcc dot gnu.org
2021-03-29 21:45 ` hubicka at gcc dot gnu.org
2021-03-30  7:20 ` rguenth at gcc dot gnu.org
2021-03-30  8:49 ` hubicka at gcc dot gnu.org
2021-03-30  9:00 ` hubicka at gcc dot gnu.org
2021-03-30 12:16 ` hubicka at gcc dot gnu.org
2021-03-31  9:18 ` doko at debian dot org
2021-03-31  9:18 ` doko at gcc dot gnu.org
2021-03-31  9:19 ` doko at gcc dot gnu.org
2021-03-31  9:33 ` hubicka at ucw dot cz
2021-03-31  9:35 ` cvs-commit at gcc dot gnu.org
2021-03-31  9:39 ` hubicka at ucw dot cz
2021-03-31 18:10 ` cvs-commit at gcc dot gnu.org
2021-03-31 18:12 ` hubicka at gcc dot gnu.org
2021-04-01 12:50 ` doko at debian dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99447-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).