public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rmathew@hotmail.com
Subject: Re: c++/8656: Unable to assign function with __attribute__ and pointer return type to an appropriate variable
Date: Thu, 05 Dec 2002 05:54:00 -0000	[thread overview]
Message-ID: <20021205135416.24944.qmail@sources.redhat.com> (raw)

Synopsis: Unable to assign function with __attribute__ and pointer return type to an appropriate variable

State-Changed-From-To: open->analyzed
State-Changed-By: cae
State-Changed-When: Thu Dec  5 05:54:11 2002
State-Changed-Why:
    I'm not sure if this is a bug or nor. The problem is that the
    types actually differ because the attribute applies to different
    parts of the declaration. In
    
    int * __attribute__((stdcall)) F (void) {};
    
    the attribute is applied to the return type not to the function type.
    In the extern declaration
    
    extern int * (__attribute__((stdcall)) * f) (void);
    
    the attribute is applied to the function type. I'm not 100% sure if
    this is intended or a parser error but I suspect it is intended.
    
    As a result of this the error itself is justified because calling
    conventions for the function and the function pointer differ. The
    text of the error however isn't helful at all.
    
    Workaround: Put explicit parenthesis around the attribute and
    the function name:
    
    int * (__attribute__(stdcall)) F) (void) {};
    
       regards  Christian
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8656


             reply	other threads:[~2002-12-05 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  5:54 ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-28  7:31 rmathew

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=20021205135416.24944.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rmathew@hotmail.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).