public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109047] Harmonize __attribute__((target_clones)) requirement in function prototype
Date: Tue, 07 Mar 2023 06:29:29 +0000	[thread overview]
Message-ID: <bug-109047-4-ORhVvBXwEG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109047-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
More over the idea of this attribute is you only need to say on the definition
if there is going to be multiple targets. Otherwise you would get different
behavior across targets. And exporting different symbols if you have one
version of the code with and without it. E.g. you have a shared library with a
static abi.

      parent reply	other threads:[~2023-03-07  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  6:01 [Bug c++/109047] New: " hbucher at gmail dot com
2023-03-07  6:14 ` [Bug c++/109047] " pinskia at gcc dot gnu.org
2023-03-07  6:29 ` pinskia at gcc dot gnu.org [this message]

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-109047-4-ORhVvBXwEG@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).