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 ipa/114985] [15 regression] internal compiler error: in discriminator_fail during stage2
Date: Wed, 08 May 2024 17:06:35 +0000 [thread overview]
Message-ID: <bug-114985-4-wXgKY76pb7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114985-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |15.0
Keywords| |needs-reduction
CC| |pinskia at gcc dot gnu.org
Component|bootstrap |ipa
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #4)
>
> If <POINTER> = <POINTER> OP_EQUAL <POINTER> is valid gimple, then we should
> change operator_equal::fold_range() to accept all pointer operands. If not,
> then we need to change the IPA pass.
>
> I would appreciate if an IL expert could opine here.
`POINTER = POINTER CMP POINTER` should be invalid gimple as far as I can tell.
The result of CMP should be a boolean type (except for vector compares where it
is a vector boolean type). We have ran into these issues before with pointer
types even.
I might get some time later today to reduce the testcase too.
next prev parent reply other threads:[~2024-05-08 17:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 12:59 [Bug bootstrap/114985] New: " seurer at gcc dot gnu.org
2024-05-08 15:00 ` [Bug bootstrap/114985] " seurer at gcc dot gnu.org
2024-05-08 15:35 ` aldyh at gcc dot gnu.org
2024-05-08 16:34 ` seurer at gcc dot gnu.org
2024-05-08 16:34 ` aldyh at gcc dot gnu.org
2024-05-08 17:06 ` pinskia at gcc dot gnu.org [this message]
2024-05-08 20:33 ` [Bug ipa/114985] " aldyh at gcc dot gnu.org
2024-05-08 22:28 ` seurer at gcc dot gnu.org
2024-05-09 14:21 ` seurer at gcc dot gnu.org
2024-05-09 16:27 ` dje at gcc dot gnu.org
2024-05-09 21:54 ` aldyh at gcc dot gnu.org
2024-05-09 22:36 ` aldyh at gcc dot gnu.org
2024-05-10 9:27 ` aldyh at gcc dot gnu.org
2024-05-10 12:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-10 12:49 ` hubicka at gcc dot gnu.org
2024-05-10 14:38 ` segher at gcc dot gnu.org
2024-05-10 16:15 ` jamborm at gcc dot gnu.org
2024-05-11 9:47 ` aldyh at gcc dot gnu.org
2024-05-11 9:48 ` aldyh at gcc dot gnu.org
2024-05-13 14:06 ` jamborm at gcc dot gnu.org
2024-05-15 20:49 ` jamborm at gcc dot gnu.org
2024-05-15 21:06 ` amacleod at redhat dot com
2024-05-16 8:16 ` aldyh at gcc dot gnu.org
2024-05-16 9:59 ` cvs-commit at gcc dot gnu.org
2024-05-16 9:59 ` cvs-commit at gcc dot gnu.org
2024-05-16 10:07 ` aldyh at gcc dot gnu.org
2024-05-16 10:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 11:49 ` aldyh at gcc dot gnu.org
2024-05-16 11:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 12:50 ` aldyh at gcc dot gnu.org
2024-05-16 12:56 ` aldyh at gcc dot gnu.org
2024-05-16 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-16 14:24 ` aldyh at gcc dot gnu.org
2024-05-16 19:06 ` segher 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-114985-4-wXgKY76pb7@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).