public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103845] ICE in execute, at gimple-harden-conditionals.cc:552 -fharden-compares -fno-ipa-pure-const and returns_twice Date: Thu, 17 Feb 2022 15:33:07 +0000 [thread overview] Message-ID: <bug-103845-4-3VQoSrDEDa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103845-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103845 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |104263 --- Comment #4 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- I'm pretty sure it was the patch for bug 104263 that fixed it. Confirming... Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104263 [Bug 104263] [10/11 Regression] '-fcompare-debug' failure (length) w/ -O2 -fnon-call-exceptions -fno-inline-small-functions since r10-3575-g629387a6586a7531
next prev parent reply other threads:[~2022-02-17 15:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-27 10:19 [Bug tree-optimization/103845] New: ICE in execute, at gimple-harden-conditionals.cc:552 asolokha at gmx dot com 2021-12-28 2:25 ` [Bug tree-optimization/103845] " pinskia at gcc dot gnu.org 2022-02-17 12:58 ` [Bug tree-optimization/103845] ICE in execute, at gimple-harden-conditionals.cc:552 -fharden-compares -fno-ipa-pure-const and returns_twice aoliva at gcc dot gnu.org 2022-02-17 13:07 ` asolokha at gmx dot com 2022-02-17 15:33 ` aoliva at gcc dot gnu.org [this message] 2022-02-17 16:44 ` aoliva at gcc dot gnu.org 2022-02-25 1:20 ` cvs-commit at gcc dot gnu.org 2022-02-25 1:44 ` aoliva at gcc dot gnu.org 2022-05-10 10:19 ` jakub 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-103845-4-3VQoSrDEDa@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).