public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109578] fail to remove dead code due to division by zero
Date: Thu, 20 Apr 2023 21:49:30 +0000 [thread overview]
Message-ID: <bug-109578-4-8xcUxf9L9L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109578-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109578
--- Comment #4 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Andrew Pinski from comment #3)
> Anyways maybe the issue with PR 29968 was a scheduling issue which was fixed
> later on that GCC didn't realize divide could trap.
OK, thanks, I can see your update marking PR 29968 as a duplicate of PR 41239
(fixed).
next prev parent reply other threads:[~2023-04-20 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 21:17 [Bug middle-end/109578] New: " vincent-gcc at vinc17 dot net
2023-04-20 21:18 ` [Bug middle-end/109578] " pinskia at gcc dot gnu.org
2023-04-20 21:26 ` vincent-gcc at vinc17 dot net
2023-04-20 21:37 ` pinskia at gcc dot gnu.org
2023-04-20 21:49 ` vincent-gcc at vinc17 dot net [this message]
2023-04-20 21:50 ` 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-109578-4-8xcUxf9L9L@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).