public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96125] __attribute__((target("cpu=power10,mma"))) does not set TARGET_MMA
Date: Fri, 10 Jul 2020 15:12:49 +0000	[thread overview]
Message-ID: <bug-96125-4-dHg6Vgcqtc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96125-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96125

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:

https://gcc.gnu.org/g:45b7f80f2e591d4f674d2f0798d31d51a7e46a72

commit r10-8458-g45b7f80f2e591d4f674d2f0798d31d51a7e46a72
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Thu Jul 9 15:52:59 2020 -0500

    rs6000: Allow MMA built-in initialization regardless of compiler options

    Built-in initialization occurs only once and fairly early, when the
    command line options are in force.  If the -mcpu=<CPU> is pre-power10,
    then we fail to initialize the MMA built-ins, so they are not
    available to call in a #pragma target/attribute target function.
    The fix is to basically always (on server type cpus) initialize the MMA
    built-ins so we can use them in #pragma target/attribute target functions.

    2020-07-09  Peter Bergner  <bergner@linux.ibm.com>

    gcc/
            PR target/96125
            * config/rs6000/rs6000-call.c (rs6000_init_builtins): Define the
MMA
            specific types __vector_quad and __vector_pair, and initialize the
            MMA built-ins if TARGET_EXTRA_BUILTINS is set.
            (mma_init_builtins): Don't test for mask set in
rs6000_builtin_mask.
            Remove now unneeded mask variable.
            * config/rs6000/rs6000.c (rs6000_option_override_internal): Add the
            OPTION_MASK_MMA flag for power10 if not already set.

    gcc/testsuite/
            PR target/96125
            * gcc.target/powerpc/pr96125.c: New test.

    (cherry picked from commit fd263be4b523ff1b7f7dda49d856cc57221e8d21)

  parent reply	other threads:[~2020-07-10 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 20:08 [Bug target/96125] New: " bergner at gcc dot gnu.org
2020-07-08 20:10 ` [Bug target/96125] " bergner at gcc dot gnu.org
2020-07-08 20:55 ` bergner at gcc dot gnu.org
2020-07-08 22:09 ` bergner at gcc dot gnu.org
2020-07-09 20:59 ` cvs-commit at gcc dot gnu.org
2020-07-09 23:20 ` bergner at gcc dot gnu.org
2020-07-10 15:12 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-10 15:29 ` bergner 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-96125-4-dHg6Vgcqtc@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).