public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107156] New: ice in lookup_attribute_by_prefix, at attribs.h:239
Date: Wed, 05 Oct 2022 10:09:39 +0000	[thread overview]
Message-ID: <bug-107156-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107156
           Summary: ice in lookup_attribute_by_prefix, at attribs.h:239
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For testsuite file ./gcc.dg/c2x-attr-noreturn-1.c, with recent gcc, I get this:

[/home/dcb/gcc/trunk.git/gcc/testsuite] $ /home/dcb/gcc/results/bin/gcc -c -w
-O2 ./gcc.dg/c2x-attr-noreturn-1.c
during IPA pass: icf
./gcc.dg/c2x-attr-noreturn-1.c:56:1: internal compiler error: in
lookup_attribute_by_prefix, at attribs.h:239
   56 | [[noreturn]] int main ();
      | ^
0x1bd9afe lookup_attribute_by_prefix(char const*, tree_node*)
        ../../trunk.git/gcc/attribs.h:239

Please not I am not using any -std= flag.

The bug first seems to occur sometime between git hash f758d447d7f46992
and 43faf3e5445b5717, which is about 50 commits.

             reply	other threads:[~2022-10-05 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 10:09 dcb314 at hotmail dot com [this message]
2022-10-05 10:10 ` [Bug c/107156] " dcb314 at hotmail dot com
2022-10-05 10:27 ` marxin at gcc dot gnu.org
2022-10-05 11:43 ` [Bug c/107156] ICE in lookup_attribute_by_prefix, at attribs.h:239 since r13-2976-g3a3516bc4a0a0307 marxin at gcc dot gnu.org
2022-10-05 11:50 ` marxin at gcc dot gnu.org
2022-10-05 12:53 ` cvs-commit at gcc dot gnu.org
2022-10-05 12:54 ` marxin 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-107156-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).