public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: zack@codesourcery.com,  gcc@gcc.gnu.org
Subject: Re: #pragma redefine_extname and local declarations
Date: Wed, 22 Sep 2004 04:34:00 -0000	[thread overview]
Message-ID: <4150AD06.8030805@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409211536490.5782@digraph.polyomino.org.uk>

Joseph S. Myers wrote:

>On Mon, 20 Sep 2004, Mark Mitchell wrote:
>
>  
>
>>This did not work in GCC 3.4 either, so I don't think it had anything to do
>>with Zack's changes to redefine_extname in GCC 4.0.  But, I'd be curious as to
>>whether or not you think that this behavior is as desired.  If you don't think
>>this is the desired behavior, then perhaps we should be calling
>>maybe_apply_renaming_pragma more often -- after every function declaration
>>with external linkage in finish_decl, rather than just those with global
>>scope.
>>    
>>
>
>I think the pragma should apply to all external function declarations (and 
>this should probably be the case for extern_prefix as well), explicit and 
>implicit.  This also appears to be what the Solaris 9 compiler does.
>  
>
Indeed.  I am testing a patch to fix this bug.

Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

      reply	other threads:[~2004-09-21 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21  3:34 Mark Mitchell
2004-09-21 16:11 ` Joseph S. Myers
2004-09-22  4:34   ` Mark Mitchell [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=4150AD06.8030805@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm@polyomino.org.uk \
    --cc=zack@codesourcery.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).