From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>,
Patrick Palka <ppalka@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree: Use comdat tree_code_{type,length} even for C++11/14 [PR108634]
Date: Fri, 3 Feb 2023 09:42:11 +0100 [thread overview]
Message-ID: <Y9zI4z1w4ZvU4dDb@tucnak> (raw)
In-Reply-To: <Y9vJBTq6losUIR6J@tucnak>
On Thu, Feb 02, 2023 at 03:30:29PM +0100, Jakub Jelinek via Gcc-patches wrote:
> Tested in non-bootstrapped build with both -std=gnu++17 and -std=gnu++11,
> ok for trunk if it passes full bootstrap/regtest?
Bootstrapped/regtested successfully on x86_64-linux and i686-linux
(gcc 12 as stage1 compiler) and on powerpc64le-linux (gcc 4.8.5 as
stage1 compiler, testing the other paths).
> 2023-02-02 Jakub Jelinek <jakub@redhat.com>
>
> PR plugins/108634
> * tree-core.h (tree_code_type, tree_code_length): For C++11 or
> C++14, don't declare as extern const arrays.
> (tree_code_type_tmpl, tree_code_length_tmpl): New types with
> static constexpr member arrays for C++11 or C++14.
> * tree.h (TREE_CODE_CLASS): For C++11 or C++14 use
> tree_code_type_tmpl <0>::tree_code_type instead of tree_code_type.
> (TREE_CODE_LENGTH): For C++11 or C++14 use
> tree_code_length_tmpl <0>::tree_code_length instead of
> tree_code_length.
> * tree.cc (tree_code_type, tree_code_length): Remove.
Jakub
next prev parent reply other threads:[~2023-02-03 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:30 Jakub Jelinek
2023-02-03 8:42 ` Jakub Jelinek [this message]
2023-03-10 9:05 ` Patch ping - " Jakub Jelinek
2023-03-10 9:32 ` Richard Biener
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=Y9zI4z1w4ZvU4dDb@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ppalka@redhat.com \
--cc=rguenther@suse.de \
/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).