From: Mark Mitchell <mark@codesourcery.com>
To: Robert Lipe <robertlipe@usa.net>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: 3.2 branch/openserver g++ test results looking bad
Date: Thu, 24 Oct 2002 09:21:00 -0000 [thread overview]
Message-ID: <24980000.1035445270@warlock.codesourcery.com> (raw)
In-Reply-To: <20021023175229.GJ5058@rjlhome.caldera.com>
> 3.0.4 didn't do this. You can argue that the assembler is being lame
> and I won't argue, but it'd be helpful to folks that use AT&T derived
> assemblers if we wouldn't torment them.
>
> Can anyone offer a hand on this?
First, we need to get a high-priority PR open for this, if you want
me to notice. :-)
Perhaps you're getting burned by:
#undef ASM_OUTPUT_EXTERNAL_LIBCALL
#define ASM_OUTPUT_EXTERNAL_LIBCALL(FILE, FUN) \
if (TARGET_ELF) (*targetm.asm_out.globalize_label) (FILE, XSTR (FUN, 0))
(I'm just grepping around for globalization things that are in sco5.h
but not elsewhere...)
Set a breakpoint on default_globalize_label and see where the two
calls are coming from.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-10-24 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 15:58 Robert Lipe
2002-10-24 9:21 ` Mark Mitchell [this message]
2002-10-24 15:31 ` Robert Lipe
2002-10-24 15:52 ` Daniel Jacobowitz
2002-10-24 21:15 ` Robert Lipe
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=24980000.1035445270@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=robertlipe@usa.net \
/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).