public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/113183] LTO crashes with Segmentation fault Date: Sat, 30 Dec 2023 19:43:41 +0000 [thread overview] Message-ID: <bug-113183-4-B3hBqdrEZZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113183-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113183 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- But changing env to Ubuntu, upstream GCC produces an ICE: ``` Segmentation fault 0xf370cf crash_signal /home/apinski/src/upstream-gcc/gcc/gcc/toplev.cc:316 0x7f1bac5a351f ??? ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0xf940b6 default_tree_printer(pretty_printer*, text_info*, char const*, int, bool, bool, bool, bool*, char const**) /home/apinski/src/upstream-gcc/gcc/gcc/tree-diagnostic.cc:274 0xf940b6 default_tree_printer(pretty_printer*, text_info*, char const*, int, bool, bool, bool, bool*, char const**) /home/apinski/src/upstream-gcc/gcc/gcc/tree-diagnostic.cc:251 0x21d2ef4 pp_format(pretty_printer*, text_info*, urlifier const*) /home/apinski/src/upstream-gcc/gcc/gcc/pretty-print.cc:1602 0x21ad9cb diagnostic_context::report_diagnostic(diagnostic_info*) /home/apinski/src/upstream-gcc/gcc/gcc/diagnostic.cc:1604 0x21b1dd7 diagnostic_impl /home/apinski/src/upstream-gcc/gcc/gcc/diagnostic.cc:1767 0x21b1dd7 warning(int, char const*, ...) /home/apinski/src/upstream-gcc/gcc/gcc/diagnostic.cc:1900 0x12bdd17 switch_to_section(section*, tree_node*) /home/apinski/src/upstream-gcc/gcc/gcc/varasm.cc:7935 0x12c9cd2 assemble_variable(tree_node*, int, int, int) /home/apinski/src/upstream-gcc/gcc/gcc/varasm.cc:2407 0x12ce2f9 varpool_node::assemble_decl() /home/apinski/src/upstream-gcc/gcc/gcc/varpool.cc:596 0x12cee6e varpool_node::assemble_decl() /home/apinski/src/upstream-gcc/gcc/gcc/varpool.cc:568 0x12cee6e symbol_table::output_variables() /home/apinski/src/upstream-gcc/gcc/gcc/varpool.cc:764 0xa4865a symbol_table::compile() /home/apinski/src/upstream-gcc/gcc/gcc/cgraphunit.cc:2402 0x9951d1 lto_main() /home/apinski/src/upstream-gcc/gcc/gcc/lto/lto.cc:685 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. lto-wrapper: fatal error: /home/apinski/upstream-gcc/bin/gcc returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status ```
next prev parent reply other threads:[~2023-12-30 19:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 19:35 [Bug lto/113183] New: " sebunger44 at gmail dot com 2023-12-30 19:40 ` [Bug lto/113183] " pinskia at gcc dot gnu.org 2023-12-30 19:43 ` pinskia at gcc dot gnu.org [this message] 2023-12-30 19:44 ` pinskia at gcc dot gnu.org 2023-12-30 19:45 ` sebunger44 at gmail dot com 2023-12-30 19:46 ` pinskia at gcc dot gnu.org 2023-12-30 19:48 ` pinskia at gcc dot gnu.org 2023-12-30 19:48 ` sebunger44 at gmail dot com 2023-12-30 19:49 ` sebunger44 at gmail dot com 2023-12-30 19:49 ` sebunger44 at gmail dot com 2023-12-30 19:54 ` pinskia at gcc dot gnu.org 2023-12-30 20:00 ` sebunger44 at gmail dot com 2023-12-30 20:20 ` pinskia at gcc dot gnu.org 2023-12-30 20:25 ` sebunger44 at gmail dot com
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-113183-4-B3hBqdrEZZ@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: linkBe 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).