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/98688] [modules] does not work on PowerPC with opaque MMA types vector_pair/vector_quad
Date: Tue, 12 Mar 2024 13:42:11 +0000	[thread overview]
Message-ID: <bug-98688-4-rXe004Ep1v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98688-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>:

https://gcc.gnu.org/g:4aa87b856067d4911de8fb66b3a27659dc75ca6d

commit r14-9439-g4aa87b856067d4911de8fb66b3a27659dc75ca6d
Author: Nathaniel Shead <nathanieloshead@gmail.com>
Date:   Sun Mar 10 22:06:18 2024 +1100

    c++: Support target-specific nodes when streaming modules [PR111224]

    Some targets make use of POLY_INT_CSTs and other custom builtin types,
    which currently violate some assumptions when streaming. This patch adds
    support for them, such as types like Aarch64 __fp16, PowerPC __ibm128,
    and vector types thereof.

    This patch doesn't provide "full" support of AArch64 SVE, however, since
    for that we would need to support 'target' nodes (tracked in PR108080).

    Adding the new builtin types means that on Aarch64 we now have 217
    global trees created on initialisation (up from 191), so this patch also
    slightly bumps the initial size of the fixed_trees allocation to 250.

            PR c++/98645
            PR c++/98688
            PR c++/111224

    gcc/cp/ChangeLog:

            * module.cc (enum tree_tag): Add new tag for builtin types.
            (trees_out::start): POLY_INT_CSTs can be emitted.
            (trees_in::start): Likewise.
            (trees_out::core_vals): Stream POLY_INT_CSTs.
            (trees_in::core_vals): Likewise.
            (trees_out::type_node): Handle vectors with multiple coeffs.
            (trees_in::tree_node): Likewise.
            (init_modules): Register target-specific builtin types. Bump
            initial capacity slightly.

    gcc/testsuite/ChangeLog:

            * g++.dg/modules/target-aarch64-1_a.C: New test.
            * g++.dg/modules/target-aarch64-1_b.C: New test.
            * g++.dg/modules/target-powerpc-1_a.C: New test.
            * g++.dg/modules/target-powerpc-1_b.C: New test.
            * g++.dg/modules/target-powerpc-2_a.C: New test.
            * g++.dg/modules/target-powerpc-2_b.C: New test.

    Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
    Reviewed-by: Patrick Palka <ppalka@redhat.com>

  parent reply	other threads:[~2024-03-12 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 18:22 [Bug target/98688] New: C++ modules support " acsawdey at gcc dot gnu.org
2021-01-14 18:34 ` [Bug target/98688] " acsawdey at gcc dot gnu.org
2021-01-15 13:25 ` nathan at gcc dot gnu.org
2021-01-15 18:01 ` acsawdey at gcc dot gnu.org
2024-03-12 13:42 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-12 13:44 ` [Bug target/98688] [modules] " nshead 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-98688-4-rXe004Ep1v@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).