From: David Edelsohn <dje.gcc@gmail.com>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Perry Smith <pedzsan@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: AIX library issues
Date: Tue, 25 Oct 2011 15:14:00 -0000 [thread overview]
Message-ID: <CAGWvnynT=CWpcJMBttHC3nrtrL+Vno=Hz+vDS369OBYPonCfiQ@mail.gmail.com> (raw)
In-Reply-To: <20111025081546.GA62410@adacore.com>
On Tue, Oct 25, 2011 at 4:15 AM, Arnaud Charlet <charlet@adacore.com> wrote:
>> I wonder if it might make sense to more strongly suggest to use GNU as
>> on AIX? The install manual currently says
>>
>> The native @command{as} and @command{ld} are recommended for
>> bootstrapping
>> on AIX@. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20
>> is required to bootstrap on AIX 5@. The native AIX tools do
>> interoperate with GCC@.
>>
>> What's the downside of not using the native AIX tools at all (assembler
>> and linker)?
>
> FWIW, we've recently made this choice/switch for GNAT at AdaCore, which
> allows us in particular to use dwarf-2/3 debug info.
Is AdaCore maintaining GNU Binutils on AIX? I do not believe that
Binutils implements some toolchain changes to AIX 6.1 and AIX 7.1.
Using Binutils means someone keeping it up to date with AIX. On the
other hand, if there is enough external interest in GNU Binutils, IBM
may lose control of the toolchain for its platform.
Thanks, David
next prev parent reply other threads:[~2011-10-25 14:10 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
[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 [this message]
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='CAGWvnynT=CWpcJMBttHC3nrtrL+Vno=Hz+vDS369OBYPonCfiQ@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=charlet@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=pedzsan@gmail.com \
--cc=richard.guenther@gmail.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).