public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "t.josefowitz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100061] [10/11 Regression] Comparison guarding undefined behaviour disappears
Date: Tue, 13 Apr 2021 14:06:19 +0000	[thread overview]
Message-ID: <bug-100061-4-ptuoz1OKUB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100061-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Tobias S. Josefowitz <t.josefowitz at gmail dot com> ---
Richard - I ran into this in a real world application.

  parent reply	other threads:[~2021-04-13 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 10:15 [Bug c/100061] New: " t.josefowitz at gmail dot com
2021-04-13 11:45 ` [Bug tree-optimization/100061] " rguenth at gcc dot gnu.org
2021-04-13 11:52 ` rguenth at gcc dot gnu.org
2021-04-13 12:01 ` [Bug tree-optimization/100061] [10/11 Regression] " jakub at gcc dot gnu.org
2021-04-13 13:00 ` jakub at gcc dot gnu.org
2021-04-13 13:32 ` jakub at gcc dot gnu.org
2021-04-13 13:49 ` rguenth at gcc dot gnu.org
2021-04-13 13:52 ` rguenth at gcc dot gnu.org
2021-04-13 13:56 ` jakub at gcc dot gnu.org
2021-04-13 14:06 ` t.josefowitz at gmail dot com [this message]
2021-08-23 20:06 ` [Bug tree-optimization/100061] [10/11/12 " t.josefowitz at gmail dot com
2021-08-24  6:47 ` rguenth at gcc dot gnu.org
2022-06-28 10:44 ` [Bug tree-optimization/100061] [10/11/12/13 " jakub at gcc dot gnu.org
2023-01-18 16:55 ` jakub at gcc dot gnu.org
2023-01-19 13:22 ` [Bug tree-optimization/100061] [10/11 " rguenth at gcc dot gnu.org
2023-07-07 10:39 ` [Bug tree-optimization/100061] [11 " rguenth 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-100061-4-ptuoz1OKUB@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).