public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107308] New: ICE in expand_fn_using_insn, at internal-fn.cc:153 Date: Tue, 18 Oct 2022 17:45:59 +0000 [thread overview] Message-ID: <bug-107308-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107308 Bug ID: 107308 Summary: ICE in expand_fn_using_insn, at internal-fn.cc:153 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r9 and file gcc.dg/gimplefe-26.c : $ gcc-13-20221016 -c gimplefe-26.c -fgimple during RTL pass: expand gimplefe-26.c: In function 'foo_1': gimplefe-26.c:5:18: internal compiler error: in expand_fn_using_insn, at internal-fn.cc:153 5 | type __GIMPLE () foo_##num (type a, type b, type c) \ | ^~~~ gimplefe-26.c:12:1: note: in expansion of macro 'foo' 12 | foo(float, 1) | ^~~ 0xbe62ff expand_fn_using_insn ../../gcc/internal-fn.cc:153 0x960647 expand_call_stmt ../../gcc/cfgexpand.cc:2737 0x960647 expand_gimple_stmt_1 ../../gcc/cfgexpand.cc:3880 0x960647 expand_gimple_stmt ../../gcc/cfgexpand.cc:4044 0x967def expand_gimple_basic_block ../../gcc/cfgexpand.cc:6096 0x96a446 execute ../../gcc/cfgexpand.cc:6822
next reply other threads:[~2022-10-18 17:45 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 17:45 gscfq@t-online.de [this message] 2022-10-19 6:51 ` [Bug c/107308] " marxin at gcc dot gnu.org 2022-10-19 7:23 ` 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-107308-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: 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).