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/108449] New: [13 Regression] ICE in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 Date: Wed, 18 Jan 2023 18:22:00 +0000 [thread overview] Message-ID: <bug-108449-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108449 Bug ID: 108449 Summary: [13 Regression] ICE in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 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 between 20220904 and 20220911, at -O1+ : $ cat z1.c static int vfork(); void f() { vfork(); } $ gcc-13-20230115 -c z1.c -O2 z1.c:1:12: warning: 'vfork' used but never defined 1 | static int vfork(); | ^~~~~ during GIMPLE pass: cddce z1.c: In function 'f': z1.c:2:1: internal compiler error: in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 2 | void f() { vfork(); } | ^~~~ 0xe0f0dc eliminate_unnecessary_stmts ../../gcc/tree-ssa-dce.cc:1512 0xe108bf perform_tree_ssa_dce ../../gcc/tree-ssa-dce.cc:1945 0xe11e55 tree_ssa_cd_dce ../../gcc/tree-ssa-dce.cc:1986 0xe11e55 execute ../../gcc/tree-ssa-dce.cc:2069
next reply other threads:[~2023-01-18 18:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 18:22 gscfq@t-online.de [this message] 2023-01-18 19:14 ` [Bug tree-optimization/108449] " pinskia at gcc dot gnu.org 2023-01-19 7:43 ` rguenth at gcc dot gnu.org 2023-01-19 7:46 ` rguenth at gcc dot gnu.org 2023-01-23 7:27 ` cvs-commit at gcc dot gnu.org 2023-01-23 7:28 ` rguenth at gcc dot gnu.org 2023-01-25 9:20 ` 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-108449-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).