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 middle-end/54664] expand_gimple_cond -Wtype-limits warning for predictably small BRANCH_COST Date: Thu, 11 Apr 2024 02:28:14 +0000 [thread overview] Message-ID: <bug-54664-4-MzDM7NXa5Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54664-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54664 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |6.0 Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed in GCC 6 by r6-3577-gef295bcefe9791 (though BRANCH_COST changed again in GCC 9 to be defined as 1 in r9-1500-gb4324a144b4499 ).
prev parent reply other threads:[~2024-04-11 2:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-21 18:36 [Bug middle-end/54664] New: expand_gimple_cond " amylaar at gcc dot gnu.org 2014-07-29 11:10 ` [Bug middle-end/54664] " hp at gcc dot gnu.org 2021-03-19 22:01 ` [Bug middle-end/54664] expand_gimple_cond -Wtype-limits " egallager at gcc dot gnu.org 2021-03-19 22:08 ` paulkoning at comcast dot net 2024-04-11 2:28 ` pinskia at gcc dot gnu.org [this message]
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-54664-4-MzDM7NXa5Q@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).