public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102347] "fatal error: target specific builtin not available" with MMA and LTO
Date: Wed, 15 Dec 2021 08:13:15 +0000 [thread overview]
Message-ID: <bug-102347-4-i0pXO8BHlJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102347-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102347
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Kewen Lin <linkw at gcc dot gnu.org> ---
Fixed on trunk and backported to all active release branches.
Note that gcc-9 has some difference from the original commit on trunk since it
doesn't support power10 and its rs6000_builtin_decl isn't factored out either.
So I cooked one different test case which doesn't require power10 but still has
the same test coverage. As testing, the case works on ppc64le Power9 and ppc64
Power8 (BE), which can expose the original problem and pass with the fix now.
The patch against gcc-9 was also bootstrapped and regress-tested on ppc64le
Power9.
next prev parent reply other threads:[~2021-12-15 8:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:18 [Bug lto/102347] New: " chip.kerchner at ibm dot com
2021-09-15 13:20 ` [Bug lto/102347] " linkw at gcc dot gnu.org
2021-09-15 13:36 ` [Bug target/102347] " rguenth at gcc dot gnu.org
2021-09-16 10:36 ` linkw at gcc dot gnu.org
2021-09-17 9:10 ` linkw at gcc dot gnu.org
2021-09-17 9:20 ` pinskia at gcc dot gnu.org
2021-09-17 14:15 ` marxin at gcc dot gnu.org
2021-09-21 23:53 ` bergner at gcc dot gnu.org
2021-09-23 6:51 ` linkw at gcc dot gnu.org
2021-09-23 7:08 ` linkw at gcc dot gnu.org
2021-09-23 7:26 ` rguenther at suse dot de
2021-11-26 1:59 ` linkw at gcc dot gnu.org
2021-11-30 4:51 ` cvs-commit at gcc dot gnu.org
2021-12-01 18:17 ` cvs-commit at gcc dot gnu.org
2021-12-10 13:31 ` wschmidt at gcc dot gnu.org
2021-12-15 5:48 ` cvs-commit at gcc dot gnu.org
2021-12-15 6:15 ` cvs-commit at gcc dot gnu.org
2021-12-15 8:05 ` cvs-commit at gcc dot gnu.org
2021-12-15 8:13 ` linkw at gcc dot gnu.org [this message]
2021-12-15 8:25 ` linkw 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-102347-4-i0pXO8BHlJ@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).