public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm at polyomino dot org dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/17251] visibility changes not backward compatible
Date: Tue, 31 Aug 2004 13:12:00 -0000	[thread overview]
Message-ID: <20040831131205.3688.qmail@sourceware.org> (raw)
In-Reply-To: <20040831125523.17251.jakub@gcc.gnu.org>


------- Additional Comments From jsm at polyomino dot org dot uk  2004-08-31 13:12 -------
Subject: Re:  New: visibility changes not backward compatible

On Tue, 31 Aug 2004, jakub at gcc dot gnu dot org wrote:

> The thing unclear to me is why the attribute located in between return type
> and function name is sometimes applicable to the return type and sometimes
> to the FUNCTION_DECL.

If the return type is a sequence of declaration specifiers, the attribute 
forms one of the declaration specifiers and applies to the declaration.  
If not - for example, a return type int *__hidden - then it applies to the 
return type, as per the syntax in extend.texi.

If you want to make an attribute applied to a function return type really 
apply to the function itself, check the flags argument to the handler and 
act appropriately.  If you want an attribute in the declaration specifiers 
to apply instead to the type given in those specifiers, look at the 
handling of vector_size attributes.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17251


  reply	other threads:[~2004-08-31 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 12:55 [Bug c/17251] New: " jakub at gcc dot gnu dot org
2004-08-31 13:12 ` jsm at polyomino dot org dot uk [this message]
2004-08-31 22:46 ` [Bug c/17251] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-09-13  3:18 ` rth at gcc dot gnu dot org
2004-09-18 21:53 ` [Bug c/17251] [4.0 " jakub at gcc dot gnu dot org
2004-09-22  5:09 ` mmitchel at gcc dot gnu dot 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=20040831131205.3688.qmail@sourceware.org \
    --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).