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 target/103302] wrong code with -fharden-compares Date: Wed, 23 Feb 2022 07:42:13 +0000 [thread overview] Message-ID: <bug-103302-4-260MvGXLgd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103302-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103302 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- URL|https://gcc.gnu.org/piperma | |il/gcc-patches/2021-Decembe | |r/586370.html | --- Comment #14 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- The installed patch is wrong and will be reverted.
next prev parent reply other threads:[~2022-02-23 7:42 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-17 14:13 [Bug target/103302] New: " zsojka at seznam dot cz 2021-11-19 11:24 ` [Bug target/103302] " aoliva at gcc dot gnu.org 2021-11-26 0:30 ` wilson at gcc dot gnu.org 2021-11-26 3:28 ` wilson at gcc dot gnu.org 2021-11-26 5:20 ` wilson at gcc dot gnu.org 2021-11-28 21:24 ` aoliva at gcc dot gnu.org 2021-12-02 1:48 ` aoliva at gcc dot gnu.org 2021-12-02 6:18 ` zsojka at seznam dot cz 2021-12-02 6:25 ` zsojka at seznam dot cz 2021-12-03 9:29 ` aoliva at gcc dot gnu.org 2021-12-08 3:42 ` aoliva at gcc dot gnu.org 2021-12-08 18:19 ` wilson at gcc dot gnu.org 2021-12-09 2:39 ` cvs-commit at gcc dot gnu.org 2021-12-09 2:52 ` aoliva at gcc dot gnu.org 2022-02-23 7:42 ` aoliva at gcc dot gnu.org [this message] 2022-02-25 1:20 ` cvs-commit at gcc dot gnu.org 2022-02-25 23:28 ` aoliva at gcc dot gnu.org 2022-03-24 13:14 ` aoliva at gcc dot gnu.org 2022-12-07 2:21 ` 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-103302-4-260MvGXLgd@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).