From: Ken Raeburn <raeburn@cygnus.com>
To: "David Edelsohn" <dje@watson.ibm.com>
Cc: gas2@cygnus.com, configure@cygnus.com
Subject: Re: binutils snapshots no longer build gas
Date: Mon, 24 Apr 1995 23:06:00 -0000 [thread overview]
Message-ID: <9504250606.AA05683@cujo.cygnus.com> (raw)
In-Reply-To: <9504250358.AA51766@sandcastle.watson.ibm.com>
GAS does have some limitations with respect to XCOFF support
including the problem with included files which you mention, but I do not
understand why that is important enough to disable the AIX XCOFF
configuration of GAS. Some support is better than no support: IBM XAS still
is distributed with AIX 4.1 so one can use that if one encounters the
debugging information limitation.
I think it's a question of which works better, and what the default
should be for naive users. If the native assembler is going to work
significantly better, we can't really justify shipping to customers
paying for the end result a toolchain using the inferior GNU one
instead. If no native assembler exists (e.g., for embedded targets)
then using the GNU one makes sense.
You can of course override the top-level configure.in script and use
gas on such machines if you really want to. Even better, you can do
that, and then send in patches to make gas and bfd work really well on
XCOFF. :-)
But does building and installing gas by default really gain the
average user anything that makes up for the problems in debugging?
Apparently Jim Kingdon -- one of the gdb maintainers -- didn't think
so.
Ken
next prev parent reply other threads:[~1995-04-24 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9504230810.AA43969@sandcastle.watson.ibm.com>
1995-04-24 18:38 ` Ken Raeburn
1995-04-24 20:58 ` David Edelsohn
1995-04-24 23:06 ` Ken Raeburn [this message]
1995-04-24 23:37 ` David Edelsohn
1995-04-27 12:36 ` Ken Raeburn
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=9504250606.AA05683@cujo.cygnus.com \
--to=raeburn@cygnus.com \
--cc=configure@cygnus.com \
--cc=dje@watson.ibm.com \
--cc=gas2@cygnus.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).