public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int
Date: Mon, 14 Nov 2022 09:14:01 +0000 [thread overview]
Message-ID: <bug-107668-4-pJiAzRddq1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107668-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to David Binderman from comment #5)
> (In reply to David Binderman from comment #4)
> > (In reply to David Binderman from comment #3)
> > > Trying git revision 2d5c4a16dd833aa0.
> >
> > That looks good. Trying 59a63247992eb131.
>
> Looks bad. Trying 2a193e9df82917ea.
>
> Range is currently [2d5c4a16dd833aa0..59a63247992eb131].
2a193e9df82917ea looks bad. I could try d4c2f1d376da6fc3,
but the current range is 2d5c4a16dd833aa0..2a193e9df82917ea,
and they are all Jakub's revisions.
Over to Jakub for his best advice.
next prev parent reply other threads:[~2022-11-14 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 19:36 [Bug tree-optimization/107668] New: " zsojka at seznam dot cz
2022-11-13 21:01 ` [Bug tree-optimization/107668] " dcb314 at hotmail dot com
2022-11-13 21:32 ` dcb314 at hotmail dot com
2022-11-14 8:13 ` dcb314 at hotmail dot com
2022-11-14 8:34 ` dcb314 at hotmail dot com
2022-11-14 8:50 ` dcb314 at hotmail dot com
2022-11-14 9:14 ` dcb314 at hotmail dot com [this message]
2022-11-14 14:04 ` rguenth at gcc dot gnu.org
2022-11-14 14:28 ` jakub at gcc dot gnu.org
2022-11-15 8:19 ` jakub at gcc dot gnu.org
2022-11-15 8:29 ` jakub at gcc dot gnu.org
2022-11-15 16:26 ` aldyh at gcc dot gnu.org
2022-11-16 6:36 ` cvs-commit at gcc dot gnu.org
2022-11-16 8:23 ` 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-107668-4-pJiAzRddq1@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).