From: Geoff Keating <geoffk@geoffk.org>
To: kdh@ocsystems.com
Cc: binutils@sources.redhat.com, trix@redhat.com
Subject: Re: Who maintains or makes fixes for ld for AIX?
Date: Mon, 29 Oct 2001 12:43:00 -0000 [thread overview]
Message-ID: <200110292200.OAA00882@geoffk.org> (raw)
In-Reply-To: <F1789CA5-CC94-11D5-9963-0050E4A0C05B@ocsystems.com>
> Date: Mon, 29 Oct 2001 12:46:55 -0500
> From: Kevin Heatwole <kdh@ocsystems.com>
>
> I'm fairly new to the GCC scene, but I have a task to make a
> cross-compiler hosted on LinuxPPC and targeting AIX.
>
> I'm running into some bugs that I have yet to track down, but appear to
> be in either GAS or ld as it deals with entries in the TOC. For some
> reason, there are some entries that should just be 32-bit addresses in
> the TOC and the image ends up with extra an 32-bit zero in between some
> entries (almost as if the code thinks an address is 64-bit in some
> instances, but I am dealing with all 32-bit addresses). The resulting
> a.out doesn't run and the TOC offsets are really garbage (almost as if
> the linker thought it had located all 32-bit addresses, but had left
> unintended gaps in some of them and didn't figure in the gaps in its
> offset calculations).
>
> Anyway, I'd like to exchange a little email with whomever is maintaining
> ld and as as a cross to AIX. I'm willing to fix the problems but I
> don't want to reinvent the wheel.
I don't believe anyone has yet tried using these tools in a _cross_ to
AIX. They were developed for use natively on the machine. However,
I can't think of any fundamental reason why they shouldn't work, so
it's probably just bugs, not completely missing features.
A good person to ask is Tom Rix, <trix@redhat.com>.
--
- Geoffrey Keating <geoffk@geoffk.org>
next prev parent reply other threads:[~2001-10-29 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 9:48 Kevin Heatwole
2001-10-29 12:43 ` Geoff Keating [this message]
2001-10-31 13:40 ` Tom Rix
2001-10-31 14:51 ` Daniel Jacobowitz
2001-10-31 18:53 ` Tom Rix
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=200110292200.OAA00882@geoffk.org \
--to=geoffk@geoffk.org \
--cc=binutils@sources.redhat.com \
--cc=kdh@ocsystems.com \
--cc=trix@redhat.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).