public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: abi_tag attribute on templates [PR109715]
Date: Thu, 14 Dec 2023 15:33:21 -0500	[thread overview]
Message-ID: <7ded5b9e-4718-4a48-9d18-5a88321d2163@redhat.com> (raw)
In-Reply-To: <20231214191719.1941342-1-ppalka@redhat.com>

On 12/14/23 14:17, Patrick Palka wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
> trunk?  Do we want to condition this on abi_check (19)?

I think we do, sadly.

> -- >8 --
> 
> As with other declaration attributes, we need to look through
> TEMPLATE_DECL when looking up the abi_tag attribute.
> 
> 	PR c++/109715
> 
> gcc/cp/ChangeLog:
> 
> 	* mangle.cc (get_abi_tags): Look through TEMPLATE_DECL.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* g++.dg/abi/abi-tag25.C: New test.
> ---
>   gcc/cp/mangle.cc                     |  3 +++
>   gcc/testsuite/g++.dg/abi/abi-tag25.C | 17 +++++++++++++++++
>   2 files changed, 20 insertions(+)
>   create mode 100644 gcc/testsuite/g++.dg/abi/abi-tag25.C
> 
> diff --git a/gcc/cp/mangle.cc b/gcc/cp/mangle.cc
> index 0684f0e6038..1fbd879c116 100644
> --- a/gcc/cp/mangle.cc
> +++ b/gcc/cp/mangle.cc
> @@ -527,6 +527,9 @@ get_abi_tags (tree t)
>     if (!t || TREE_CODE (t) == NAMESPACE_DECL)
>       return NULL_TREE;
>   
> +  if (TREE_CODE (t) == TEMPLATE_DECL && DECL_TEMPLATE_RESULT (t))
> +    t = DECL_TEMPLATE_RESULT (t);
> +
>     if (DECL_P (t) && DECL_DECLARES_TYPE_P (t))
>       t = TREE_TYPE (t);
>   
> diff --git a/gcc/testsuite/g++.dg/abi/abi-tag25.C b/gcc/testsuite/g++.dg/abi/abi-tag25.C
> new file mode 100644
> index 00000000000..9847f0dccc8
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/abi/abi-tag25.C
> @@ -0,0 +1,17 @@
> +// PR c++/109715
> +// { dg-do compile { target c++11 } }
> +
> +template<class T>
> +[[gnu::abi_tag("foo")]] void fun() { }
> +
> +template void fun<int>();
> +
> +#if __cpp_variable_templates
> +template<class T>
> +[[gnu::abi_tag("foo")]] int var = 0;
> +
> +template int var<int>;
> +#endif
> +
> +// { dg-final { scan-assembler "_Z3funB3fooIiEvv" } }
> +// { dg-final { scan-assembler "_Z3varB3fooIiE" { target c++14 } } }


  reply	other threads:[~2023-12-14 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 19:17 Patrick Palka
2023-12-14 20:33 ` Jason Merrill [this message]
2023-12-14 21:08   ` Patrick Palka
2023-12-14 22:09     ` Jason Merrill
2023-12-15  0:59       ` Patrick Palka
2023-12-15  1:26         ` Jason Merrill
2023-12-18  8:54         ` [committed] testsuite: Fix up abi-tag25a.C test for C++11 Jakub Jelinek

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=7ded5b9e-4718-4a48-9d18-5a88321d2163@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ppalka@redhat.com \
    /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).