public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Luke Dalessandro <luked@cs.rochester.edu>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: extend gthr-posix.h with rwlock
Date: Thu, 05 Jun 2008 22:41:00 -0000	[thread overview]
Message-ID: <48486B79.7090404@cs.rochester.edu> (raw)
In-Reply-To: <200806051825.m55IPNZe033244@makai.watson.ibm.com>

David Edelsohn wrote:
>>>>>> Luke Dalessandro writes:
> 
> Luke> My problem is that unwind-dw2-fde.c seems to be compiled multiple times during 
> Luke> a gcc build, and sometimes my additions are found but other times they are 
> Luke> not. I am rebuilding again (AIX 5.1), and I'll post more information for 
> Luke> anyone that needs it.
> 
> Luke> In the meantime, is there a how-to anywhere that describes adding or modifying 
> Luke> gthr.h models in gcc?
> 
> 	AIX multilibs pthread support.  Unlike Linux, AIX does not provide
> weak versions of the pthread symbols when operating in single-threaded
> mode.  AIX uses gthr-aix.h, which includes gthr-posix.h or gthr-single.h
> depending on the -pthread option.

Thank you, this was indeed the problem. I added the needed stubbs in 
gthr-single.h and it now compiles fine. Unfortunately there seems to be 
something wrong with my installation of ld as linking fails with a large 
number of errors of the form:

ld: 0711-252 SEVERE ERROR: File auxiliary symbol entry 1 in object _negdi2_s.o:
         Field x_offset contains 4. Valid values are between 4 and -1.
         The object name is being substituted.

Unfortunately I have almost no experience with AIX. I'll look for a prebuilt 
ld that seems newer than mine to see if this helps the problem.

Thank you for your help.

Luke

  reply	other threads:[~2008-06-05 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 18:02 Luke Dalessandro
2008-06-05 18:27 ` David Edelsohn
2008-06-05 22:41   ` Luke Dalessandro [this message]
2008-06-05 22:59     ` David Edelsohn
2008-06-06  0:05       ` Luke Dalessandro

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=48486B79.7090404@cs.rochester.edu \
    --to=luked@cs.rochester.edu \
    --cc=dje@watson.ibm.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).