public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goon.pri.low at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112664] missed-optimization: extra comparison when reordering statements
Date: Wed, 22 Nov 2023 00:56:47 +0000	[thread overview]
Message-ID: <bug-112664-4-Z8u6MVVRns@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112664-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112664

--- Comment #4 from gooncreeper <goon.pri.low at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> Dup.
> 
> *** This bug has been marked as a duplicate of bug 105496 ***

Apologies.
Though, how are you so good at finding duplicates? What's the secret?(In reply
to Andrew Pinski from comment #3)
> (In reply to gooncreeper from comment #2)
> > Though, how are you so good at finding duplicates? What's the secret?
> 
> Everyone says I have bugzilla memorized but I don't, I am just really code
> at doing keyword searches and knowing what keywords to search for. In this
> case I searched for "canonical compare" because I knew this was a
> canonicalization issue with how GCC changed `v < 6` into `v <= 5`

Ah, if I knew the fancy names of optimizations I would probably be a bit better
at checking my finds.

      parent reply	other threads:[~2023-11-22  0:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  0:27 [Bug middle-end/112664] New: " goon.pri.low at gmail dot com
2023-11-22  0:30 ` [Bug middle-end/112664] " pinskia at gcc dot gnu.org
2023-11-22  0:31 ` pinskia at gcc dot gnu.org
2023-11-22  0:35 ` goon.pri.low at gmail dot com
2023-11-22  0:41 ` pinskia at gcc dot gnu.org
2023-11-22  0:56 ` goon.pri.low at gmail dot com [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-112664-4-Z8u6MVVRns@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: link
Be 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).