public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/97172] [11 Regression] ICE: tree code ‘ssa_name’ is not supported in LTO streams since r11-3303-g6450f07388f9fe57
Date: Tue, 23 Feb 2021 14:38:13 +0000	[thread overview]
Message-ID: <bug-97172-4-8UNiyTbRSU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97172-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #30 from Martin Liška <marxin at gcc dot gnu.org> ---
I still cannot build the affected package:

$ cat exiv.i
int main_argc;

void
foo(char[main_argc + 1]) {}

$ gcc exiv.i -flto -O2 -shared -fPIC
lto1: internal compiler error: Segmentation fault
0xd3de6a crash_signal
        /home/marxin/Programming/gcc/gcc/toplev.c:327
0xbc84f4 stream_read_tree_ref(lto_input_block*, data_in*)
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1830
0xf8a648 lto_input_ts_exp_tree_pointers
        /home/marxin/Programming/gcc/gcc/tree-streamer-in.c:905
0xf8a648 streamer_read_tree_body(lto_input_block*, data_in*, tree_node*)
        /home/marxin/Programming/gcc/gcc/tree-streamer-in.c:1087
0xbc7c49 lto_read_tree_1
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1700
0xbc85a1 lto_read_tree
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1741
0xbc85a1 lto_input_tree_1(lto_input_block*, data_in*, LTO_tags, unsigned int)
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1882
0xbc8857 lto_input_scc(lto_input_block*, data_in*, unsigned int*, unsigned
int*, bool)
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1770
0xbc88df lto_input_tree(lto_input_block*, data_in*)
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1897
0xbcab0f streamer_read_chain
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1335
0xbcab0f input_function
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1365
0xbcab0f lto_read_body_or_constructor
        /home/marxin/Programming/gcc/gcc/lto-streamer-in.c:1621
0x8cfd91 cgraph_node::get_untransformed_body()
        /home/marxin/Programming/gcc/gcc/cgraph.c:3940
0x8dbfe1 cgraph_node::expand()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:1798
0x8dd73e expand_all_functions
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:1995
0x8dd73e symbol_table::compile()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2359
0x8dd73e symbol_table::compile()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2270
0x8260c4 lto_main()
        /home/marxin/Programming/gcc/gcc/lto/lto.c:653
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.
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: fatal error: lto-wrapper failed
collect2: error: ld returned 1 exit status

  parent reply	other threads:[~2021-02-23 14:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  7:25 [Bug c/97172] New: " marxin at gcc dot gnu.org
2020-09-23  7:25 ` [Bug c/97172] " marxin at gcc dot gnu.org
2020-09-23  8:02 ` rguenth at gcc dot gnu.org
2020-09-23 23:00 ` msebor at gcc dot gnu.org
2020-10-01 13:46 ` hubicka at gcc dot gnu.org
2020-10-01 15:36 ` msebor at gcc dot gnu.org
2020-10-01 15:39 ` msebor at gcc dot gnu.org
2020-10-05 20:18 ` msebor at gcc dot gnu.org
2020-10-12 11:48 ` rguenth at gcc dot gnu.org
2020-10-15 15:10 ` marxin at gcc dot gnu.org
2020-10-18 16:42 ` hubicka at gcc dot gnu.org
2020-10-18 17:55 ` msebor at gcc dot gnu.org
2020-10-18 19:58 ` hubicka at ucw dot cz
2020-11-10  9:02 ` marxin at gcc dot gnu.org
2020-11-30 15:00 ` rguenth at gcc dot gnu.org
2020-11-30 15:29 ` msebor at gcc dot gnu.org
2020-11-30 17:32 ` msebor at gcc dot gnu.org
2020-11-30 21:02 ` hubicka at ucw dot cz
2020-12-01  1:11 ` msebor at gcc dot gnu.org
2020-12-01  7:42 ` rguenth at gcc dot gnu.org
2020-12-01 16:12 ` msebor at gcc dot gnu.org
2020-12-01 16:16   ` Jan Hubicka
2020-12-01 16:16 ` hubicka at ucw dot cz
2020-12-02  7:38 ` rguenther at suse dot de
2020-12-18 12:58 ` marxin at gcc dot gnu.org
2020-12-18 17:02 ` msebor at gcc dot gnu.org
2020-12-19  0:55 ` msebor at gcc dot gnu.org
2021-01-22  9:05 ` ktkachov at gcc dot gnu.org
2021-01-26 18:57 ` jakub at gcc dot gnu.org
2021-01-27 22:51 ` msebor at gcc dot gnu.org
2021-02-01 16:10 ` cvs-commit at gcc dot gnu.org
2021-02-01 16:12 ` msebor at gcc dot gnu.org
2021-02-19  2:28 ` msebor at gcc dot gnu.org
2021-02-19 18:07 ` cvs-commit at gcc dot gnu.org
2021-02-23 14:38 ` marxin at gcc dot gnu.org [this message]
2021-02-23 14:49 ` rguenth at gcc dot gnu.org
2021-02-23 17:16 ` msebor at gcc dot gnu.org
2021-02-23 19:20 ` msebor at gcc dot gnu.org
2021-02-24 15:59 ` cvs-commit at gcc dot gnu.org
2021-02-24 16:01 ` msebor at gcc dot gnu.org
2021-02-25 16:03 ` cvs-commit at gcc dot gnu.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-97172-4-8UNiyTbRSU@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).