From: Perry Smith <pedzsan@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: AIX library issues
Date: Mon, 24 Oct 2011 09:45:00 -0000 [thread overview]
Message-ID: <1A81E3FB-BB92-4057-AA3F-66C0FC853895@gmail.com> (raw)
In-Reply-To: <CAGWvnynNbtaAR8NfhrZQ6hz+Zo3vD7Z_V_ViSnLrzoxNTxbfig@mail.gmail.com>
On Oct 23, 2011, at 1:59 PM, David Edelsohn wrote:
> On Sun, Oct 23, 2011 at 10:16 AM, Perry Smith <pedzsan@gmail.com> wrote:
>
>> libgomp.so.1 wants libc.a, libpthreads.a, and libgcc_s.a. The first two do not present a problem. But there are four libgcc_s.a (normal, ppc64, pthread, and ppc64+pthread).
>>
>> Note that there is also four versions of libgomp.so.1 (normal, ppc64, pthread, ppc64+pthread).
>>
>> My question is: which libgcc_s.a should I link to? (this question is for each of the four versions of libgomp.so.1).
>>
>> Setting LIBPATH or whatever I do is going to override the internal path (since the internal path is broken). So, this may be a question that has never been asked or answered.
>>
>> My knee jerk is that the normal libgomp.so.1 wants the normal libgcc_s.a, the ppc64 wants the ppc64, etc. But I notice that it will always include pthread so that is what caused me to pause and ask.
>>
>> Part of me wonders if the two non-pthread versions of libgomp make any sense. I don't really know anything about libgomp.
>
> libgomp (-fopenmp) does not make sense without pthreads. -fopenmp
> implies pthreads.
>
> One thing to note: AIX tools default to 32 bit mode, although all
> systems are 64 bit, unlike GNU/Linux, which defaults to 64 bit mode
> (on x86-64 and PPC64).
>
> Only two of the four libgomp multilibs truly are necessary, but
> avoiding the non-pthread builds is not worth the trouble. The
> non-pthread libgomp libraries never will be used, unless GCC is
> invoked incorrectly. Each library, including libgomp, should list its
> multilib install directory first, e.g., ppc64 pthread would be
>
> -Wl,-blibpath:.../lib/gcc/powerpc-ibm-aix6.1.3.0/4.6.0/pthread/ppc64:.../lib/pthread/ppc64:/usr/lib:/lib
>
> and default would be
>
> -Wl,-blibpath:.../lib/gcc/powerpc-ibm-aix6.1.3.0/4.6.0:.../lib:/usr/lib:/lib
>
> The GCC build process and driver directory search process make a lot
> of assumptions that the system directories follow a Linux/SVR4/Solaris
> layout. To follow AIX style, the PPC64 and PPC32 non-reentrant
> (non-pthreads) libraries should be archived into the same file
> libgomp.a (which never would be referenced) and the reentrant
> (pthreads) libraries for PPC64 and PPC32 should be archived into
> libgomp_r.a. The benefit has not been shown to be worth the effort.
Thanks David,
One more question on this quest (drifting a little more off topic).
In my log files I see a lot of these errors:
> ld: 0711-768 WARNING: Object ../libsupc++/.libs/libsupc++convenience.a[eh_terminate.o], section 1, function .std::terminate():
> The branch at address 0x10c is not followed by a recognized no-op
> or TOC-reload instruction. The unrecognized instruction is 0x0.
The build continues and completes. I just want to make sure that I can safely ignore them. Surfing the web, sometimes I see people flag the as errors and other times not.
Thank you again,
pedz
next prev parent reply other threads:[~2011-10-24 0:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 4:48 Perry Smith
2011-10-18 8:30 ` Jonathan Wakely
2011-10-18 10:28 ` Jonathan Wakely
2011-10-18 15:37 ` David Edelsohn
2011-10-24 0:59 ` Perry Smith
2011-10-24 2:36 ` David Edelsohn
2011-10-24 9:45 ` Perry Smith [this message]
[not found] ` <5FB999D3-E0FA-4AC7-A26A-DAA4397D833F@gmail.com>
2011-10-25 6:31 ` David Edelsohn
2011-10-25 9:13 ` Richard Guenther
2011-10-25 9:24 ` Arnaud Charlet
2011-10-25 15:14 ` David Edelsohn
2011-10-25 16:05 ` Arnaud Charlet
2011-11-08 18:44 ` David Edelsohn
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=1A81E3FB-BB92-4057-AA3F-66C0FC853895@gmail.com \
--to=pedzsan@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@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).