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 ipa/108511] [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 since r13-5285-g106f99406312d7ed
Date: Wed, 25 Jan 2023 10:30:36 +0000	[thread overview]
Message-ID: <bug-108511-4-a4hGLGm5a9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Yeah, the test is normally run with -r argument, so just run it with;

g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/lto/pr88049_0.C -flto
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/lto/pr88049_0.C:12:11:
warning: ‘a< <template-parameter-1-1> >::~a() noexcept [with
<template-parameter-1-1> = {anonymous}::f]’ used but never defined
   12 |   virtual ~a();
      |           ^
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/lto/pr88049_0.C:9:28:
warning: ‘a<e> d(char) [with e = {anonymous}::f]’ used but never defined
    9 | template <typename e> a<e> d(char);
      |                            ^
during IPA pass: fnsummary
lto1: internal compiler error: in possibly_call_in_translation_unit_p, at
cgraph.cc:4184
0x6aa523 cgraph_edge::possibly_call_in_translation_unit_p()
        /home/marxin/Programming/gcc/gcc/cgraph.cc:4184
0xb65ad0 read_ipa_call_summary
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.cc:4406
0xb69a1f inline_read_section
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.cc:4616
0xb69e98 ipa_fn_summary_read
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.cc:4648
0xcedcf6 ipa_read_summaries_1
        /home/marxin/Programming/gcc/gcc/passes.cc:3001
0x8ae4e4 read_cgraph_and_symbols(unsigned int, char const**)
        /home/marxin/Programming/gcc/gcc/lto/lto-common.cc:2936
0x894892 lto_main()
        /home/marxin/Programming/gcc/gcc/lto/lto.cc:654
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: g++ returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

  parent reply	other threads:[~2023-01-25 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  8:36 [Bug ipa/108511] New: [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 ro at gcc dot gnu.org
2023-01-24  8:36 ` [Bug ipa/108511] " ro at gcc dot gnu.org
2023-01-25  9:19 ` [Bug ipa/108511] [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 since r13-5285-g106f99406312d7ed marxin at gcc dot gnu.org
2023-01-25  9:20 ` marxin at gcc dot gnu.org
2023-01-25 10:02 ` rguenth at gcc dot gnu.org
2023-01-25 10:30 ` marxin at gcc dot gnu.org [this message]
2023-01-25 12:07 ` rguenth at gcc dot gnu.org
2023-01-25 12:08 ` rguenth at gcc dot gnu.org
2023-01-29  0:01 ` hubicka at gcc dot gnu.org
2023-01-30  8:35 ` cvs-commit at gcc dot gnu.org
2023-01-30  8:35 ` rguenth 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-108511-4-a4hGLGm5a9@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).