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/113763] [14 Regression] build fails with clang++ host compiler because aarch64.cc uses C++14 constexpr.
Date: Tue, 06 Feb 2024 14:59:26 +0000	[thread overview]
Message-ID: <bug-113763-4-FHF5t1ckWI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113763-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:df9f6b934886f51c0c07220d1ee38874b69646c7

commit r14-8828-gdf9f6b934886f51c0c07220d1ee38874b69646c7
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Feb 6 15:56:50 2024 +0100

    aarch64: Fix build against libc++ in c++11 mode [PR113763]

    std::pair ctor used in tiles constexpr variable is only constexpr in C++14
    and later, it works with libstdc++ because it is marked constexpr there
even
    in C++11 mode.

    The following patch fixes it by using an unnamed local class instead of
    std::pair, and additionally changes the first element from unsigned int to
    unsigned char because 0xff has to fit into unsigned char on all hosts.

    2024-02-06  Jakub Jelinek  <jakub@redhat.com>

            PR target/113763
            * config/aarch64/aarch64.cc (aarch64_output_sme_zero_za): Change
tiles
            element from std::pair<unsigned int, char> to an unnamed struct.
            Adjust uses of tile range variable.

  parent reply	other threads:[~2024-02-06 14:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 10:13 [Bug target/113763] New: " iains at gcc dot gnu.org
2024-02-05 11:38 ` [Bug target/113763] " iains at gcc dot gnu.org
2024-02-05 11:54 ` jakub at gcc dot gnu.org
2024-02-05 12:21 ` redi at gcc dot gnu.org
2024-02-05 12:21 ` redi at gcc dot gnu.org
2024-02-05 14:57 ` rguenth at gcc dot gnu.org
2024-02-05 15:07 ` jakub at gcc dot gnu.org
2024-02-05 15:08 ` jakub at gcc dot gnu.org
2024-02-05 15:49 ` redi at gcc dot gnu.org
2024-02-05 15:53 ` iains at gcc dot gnu.org
2024-02-05 15:54 ` redi at gcc dot gnu.org
2024-02-05 21:35 ` jakub at gcc dot gnu.org
2024-02-06 10:03 ` rsandifo at gcc dot gnu.org
2024-02-06 10:05 ` jakub at gcc dot gnu.org
2024-02-06 10:34 ` jakub at gcc dot gnu.org
2024-02-06 10:38 ` rsandifo at gcc dot gnu.org
2024-02-06 10:42 ` redi at gcc dot gnu.org
2024-02-06 10:49 ` jakub at gcc dot gnu.org
2024-02-06 14:59 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-06 15:21 ` jakub at gcc dot gnu.org
2024-02-24 20:23 ` pinskia 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-113763-4-FHF5t1ckWI@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).