public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108250] [12/13 regression] llvm-tblgen miscompiled on powerpc-unknown-linux-gnu since r12-5383-g22c242342e38eb
Date: Thu, 28 Mar 2024 03:27:36 +0000 [thread overview]
Message-ID: <bug-108250-4-r4vhqsmd6x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108250-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108250
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12/13/14 regression] |[12/13 regression]
|llvm-tblgen miscompiled on |llvm-tblgen miscompiled on
|powerpc-unknown-linux-gnu |powerpc-unknown-linux-gnu
|since |since
|r12-5383-g22c242342e38eb |r12-5383-g22c242342e38eb
See Also| |https://bugs.gentoo.org/sho
| |w_bug.cgi?id=880677,
| |https://bugs.gentoo.org/sho
| |w_bug.cgi?id=875776
--- Comment #14 from Sam James <sjames at gcc dot gnu.org> ---
This seems "fixed" by r14-1909-g5a1ef1cfac0053. As a workaround, -fno-ipa-sra
-fno-ipa-modref -fno-ipa-icf works for GCC 12/13.
I don't really intend on spending more time on this though. I've got better at
debugging miscompilations since we filed this, but LLVM is still huge and not
easy for me to tackle.
next prev parent reply other threads:[~2024-03-28 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:35 [Bug c/108250] New: " sam at gentoo dot org
2022-12-28 23:55 ` [Bug c/108250] " sam at gentoo dot org
2022-12-29 0:04 ` sam at gentoo dot org
2022-12-29 0:06 ` sam at gentoo dot org
2022-12-29 2:13 ` [Bug ipa/108250] " pinskia at gcc dot gnu.org
2022-12-29 2:48 ` sam at gentoo dot org
2022-12-29 3:14 ` sam at gentoo dot org
2022-12-29 16:54 ` arsen at aarsen dot me
2022-12-29 17:22 ` arsen at aarsen dot me
2023-01-02 3:44 ` pinskia at gcc dot gnu.org
2023-01-02 3:46 ` pinskia at gcc dot gnu.org
2023-01-03 1:18 ` sam at gentoo dot org
2023-01-09 14:09 ` rguenth at gcc dot gnu.org
2023-01-13 16:59 ` segher at gcc dot gnu.org
2023-03-27 12:27 ` rguenth at gcc dot gnu.org
2023-05-08 12:26 ` [Bug ipa/108250] [12/13/14 " rguenth at gcc dot gnu.org
2023-05-14 12:06 ` arsen at gcc dot gnu.org
2024-03-28 3:27 ` sjames at gcc dot gnu.org [this message]
2024-03-28 3:31 ` [Bug ipa/108250] [12/13 " sjames 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-108250-4-r4vhqsmd6x@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).