public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103052] [9/10/11/12 Regression] Function is found to be pure looping but has a call to a noreturn function in it Date: Wed, 03 Nov 2021 08:31:06 +0000 [thread overview] Message-ID: <bug-103052-4-g1uAqtaQXM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103052-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103052 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Priority|P3 |P2 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- I believe a possible noreturn should make the function LOOPING_{CONST,PURE} (LOOPING as in possibly not normally returning). Can we bisect this?
next prev parent reply other threads:[~2021-11-03 8:31 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-02 21:45 [Bug c/103052] New: Function call omitted at -O1 optimization level tor at ccxvii dot net 2021-11-02 22:04 ` [Bug c/103052] " jakub at gcc dot gnu.org 2021-11-02 22:09 ` tor at ccxvii dot net 2021-11-02 22:15 ` [Bug middle-end/103052] " pinskia at gcc dot gnu.org 2021-11-02 22:16 ` [Bug middle-end/103052] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2021-11-02 22:19 ` tor at ccxvii dot net 2021-11-02 22:39 ` [Bug ipa/103052] " pinskia at gcc dot gnu.org 2021-11-02 22:41 ` pinskia at gcc dot gnu.org 2021-11-03 8:31 ` rguenth at gcc dot gnu.org [this message] 2021-11-03 8:35 ` [Bug ipa/103052] [9/10/11/12 Regression] Function is found to be pure looping but has a call to a noreturn function in it marxin at gcc dot gnu.org 2021-11-03 8:44 ` hubicka at gcc dot gnu.org 2021-11-19 12:47 ` hubicka at gcc dot gnu.org 2021-11-20 23:35 ` cvs-commit at gcc dot gnu.org 2021-11-20 23:40 ` cvs-commit at gcc dot gnu.org 2021-11-25 11:25 ` [Bug ipa/103052] [9/10/11 " cvs-commit at gcc dot gnu.org 2021-11-25 11:29 ` cvs-commit at gcc dot gnu.org 2021-11-25 13:29 ` cvs-commit at gcc dot gnu.org 2021-11-25 13:29 ` hubicka 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-103052-4-g1uAqtaQXM@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).