public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <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: Thu, 23 Sep 2021 07:26:06 +0000	[thread overview]
Message-ID: <bug-102347-4-OrufmOoZ2H@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

--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 23 Sep 2021, linkw at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102347
> 
> --- Comment #9 from Kewen Lin <linkw at gcc dot gnu.org> ---
> (In reply to Peter Bergner from comment #7)
> > (In reply to Martin Liška from comment #6)
> > > Quickly looking at the rs6000 code, it fails here:
> > > 
> > > #1  0x0000000011a0993c in rs6000_invalid_builtin
> > > (fncode=MMA_BUILTIN_DISASSEMBLE_ACC_INTERNAL) at
> > > ../../gcc/config/rs6000/rs6000-call.c:11643
> > > #2  0x0000000011a13134 in rs6000_builtin_decl (code=1603, initialize_p=true)
> > > at ../../gcc/config/rs6000/rs6000-call.c:13870
> > > #3  0x00000000115c3900 in unpack_ts_function_decl_value_fields
> > > (bp=0x3fffffffe2f0, expr=0x3fffaf195700) at ../../gcc/tree-streamer-in.c:361
> > > #4  0x00000000115c4790 in streamer_read_tree_bitfields (ib=0x3fffffffe6a0,
> > > data_in=0x132d1910, expr=0x3fffaf195700) at ../../gcc/tree-streamer-in.c:528
> > > #5  0x0000000010deaa28 in lto_read_tree_1 (ib=0x3fffffffe6a0,
> > > data_in=0x132d1910, expr=0x3fffaf195700) at ../../gcc/lto-streamer-in.c:1697
> > > 
> > > which relies on rs6000_builtin_mask. Note the mask is set here:
> > > rs6000_builtin_mask = rs6000_builtin_mask_calculate ();
> > > 
> > > where rs6000_builtin_mask_calculate is based on TARGET_* values.

Yeah, that's not going to work - if there are different builtin
decls for different flags then you have to use different BUILT_IN_*
codes as well.

  parent reply	other threads:[~2021-09-23  7:26 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 [this message]
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
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-OrufmOoZ2H@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).