public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/52490] RTL DCE removes trapping const libcalls Date: Fri, 02 Jun 2023 02:53:41 +0000 [thread overview] Message-ID: <bug-52490-4-ASgBcdZrzE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52490-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52490 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |6.4.0, 7.4.0, 8.1.0 Known to work| |7.5.0, 8.2.0 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- You need also -fno-delete-dead-exceptions not to remove them in newer versions for the gimple level.
next prev parent reply other threads:[~2023-06-02 2:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-05 13:16 [Bug rtl-optimization/52490] New: " rguenth at gcc dot gnu.org 2023-06-02 2:46 ` [Bug rtl-optimization/52490] " pinskia at gcc dot gnu.org 2023-06-02 2:53 ` pinskia at gcc dot gnu.org [this message] 2023-06-02 3:06 ` pinskia at gcc dot gnu.org 2023-06-02 3:14 ` pinskia 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-52490-4-ASgBcdZrzE@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).