public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__
@ 2001-12-19  0:27 Len Lattanzi
  2002-01-10 11:50 ` David Edelsohn
  0 siblings, 1 reply; 6+ messages in thread
From: Len Lattanzi @ 2001-12-19  0:27 UTC (permalink / raw)
  To: binutils

gcc2.95.2 (and the latest version of varasm.c) will generate 
.stabx "___CTOR_LIST__",22,0,0,_GLOBAL_.I._un_link__9streambuf

when configured with -with-gnu-as on AIX and compiling libio/streambuf.cc
But gas 2.11.2 will not parse beyond the second 0 in
gas/config/t-ppc.c:ppc_stabx (this seems to true in the latest sources
as well) 

So how I do get gas to accept this or reconfigure gcc to use gas/gnu
ld without gas choking?

I'm running on AIX5L and collect2 has the nasty habit of pulling in
every g++ object in every archive on the command line.

-Len

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__
  2001-12-19  0:27 PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__ Len Lattanzi
@ 2002-01-10 11:50 ` David Edelsohn
  2002-01-10 12:08   ` Len_Lattanzi
  2002-01-10 23:03   ` Tom Rix
  0 siblings, 2 replies; 6+ messages in thread
From: David Edelsohn @ 2002-01-10 11:50 UTC (permalink / raw)
  To: Len Lattanzi; +Cc: binutils

>>>>> Len Lattanzi writes:

Len> I'm running on AIX5L and collect2 has the nasty habit of pulling in
Len> every g++ object in every archive on the command line.

	gcc-2.95 does not support AIX 5L.  Neither GNU as nor AIX as will
accept that line, but GCC probably is only generating that line because it
is confused by the configuration.

	The AIX assembler and linker are recommended for use with GCC.
Using GNU ld will not change collect2's behavior of pulling in all objects
because it has to assume that symbols may be garbage collected before it
finds constructors and destructors.

	GCC 3.0 in CVS, which eventually will be released as GCC 3.0.4,
should work with AIX 5L, if an AIX assembler patch is installed.

David

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__
  2002-01-10 11:50 ` David Edelsohn
@ 2002-01-10 12:08   ` Len_Lattanzi
  2002-01-10 13:16     ` David Edelsohn
  2002-01-10 23:03   ` Tom Rix
  1 sibling, 1 reply; 6+ messages in thread
From: Len_Lattanzi @ 2002-01-10 12:08 UTC (permalink / raw)
  To: David Edelsohn; +Cc: binutils

On 2002-01-10 14:33:37 -0500, David Edelsohn wrote:
> 
> 	gcc-2.95 does not support AIX 5L.  Neither GNU as nor AIX as will
> accept that line, but GCC probably is only generating that line because it
> is confused by the configuration.
> 
> 	The AIX assembler and linker are recommended for use with GCC.
> Using GNU ld will not change collect2's behavior of pulling in all objects
> because it has to assume that symbols may be garbage collected before it
> finds constructors and destructors.
> 
> 	GCC 3.0 in CVS, which eventually will be released as GCC 3.0.4,
> should work with AIX 5L, if an AIX assembler patch is installed.
> 
> David

Thanks for the info. I was about to send you email after seeing your entry
in the gcc faq-o-matic.

Can -bnogc be used to avoid this behavior in collect2?

I'll peek at the 3.0 source and see how it marks ctors for gas on AIX.

-Len

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__
  2002-01-10 12:08   ` Len_Lattanzi
@ 2002-01-10 13:16     ` David Edelsohn
  0 siblings, 0 replies; 6+ messages in thread
From: David Edelsohn @ 2002-01-10 13:16 UTC (permalink / raw)
  To: binutils

>>>>> Len Lattanzi writes:

Len> Can -bnogc be used to avoid this behavior in collect2?

	No.  You cannot avoid collecting all objects in the Archive.

David

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__
  2002-01-10 11:50 ` David Edelsohn
  2002-01-10 12:08   ` Len_Lattanzi
@ 2002-01-10 23:03   ` Tom Rix
  2002-01-14 15:08     ` AIX PPC ld/gas problems with gcc Len Lattanzi
  1 sibling, 1 reply; 6+ messages in thread
From: Tom Rix @ 2002-01-10 23:03 UTC (permalink / raw)
  To: David Edelsohn; +Cc: binutils

David Edelsohn wrote:

>
>         The AIX assembler and linker are recommended for use with GCC.

Gnu's AIX ld and as work with gcc.    Are there some binutils issues I should
know about?

Tom

--
Tom Rix
GCC Engineer
trix@redhat.com



^ permalink raw reply	[flat|nested] 6+ messages in thread

* AIX PPC ld/gas problems with gcc
  2002-01-10 23:03   ` Tom Rix
@ 2002-01-14 15:08     ` Len Lattanzi
  0 siblings, 0 replies; 6+ messages in thread
From: Len Lattanzi @ 2002-01-14 15:08 UTC (permalink / raw)
  To: binutils

On 2002-01-10 23:16:39 -0600, Tom Rix wrote:
> Gnu's AIX ld and as work with gcc.    Are there some binutils issues I should
> know about?
> 
At least four issues with gcc/binutils/AIX

1) Linking with collect2/system linker extracts every g++ object from
   every archive on the link line

2) Linking shared library with gcc force import of __builtin_delete
   from '.' [the main exe] See
   http://gcc.gnu.org/cgi-bin/fom.cgi?file=94

3) Loading g++ shared library into JVM will fail to invoke static
   ctors [On HP I can work around this via ld +init]

4) C++EH house-keeping code is not thread-safe.

I had hoped to workaround #1 and #2 with binutils...

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-01-14 22:28 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-19  0:27 PPC XCOFF gas 2.11.2 will not parse gcc2.95.2 .stabx ___CTOR_LIST__ Len Lattanzi
2002-01-10 11:50 ` David Edelsohn
2002-01-10 12:08   ` Len_Lattanzi
2002-01-10 13:16     ` David Edelsohn
2002-01-10 23:03   ` Tom Rix
2002-01-14 15:08     ` AIX PPC ld/gas problems with gcc Len Lattanzi

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).