public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: "David Edelsohn" <dje@watson.ibm.com>
To: Ken Raeburn <raeburn@cygnus.com>
Cc: gas2@cygnus.com, configure@cygnus.com
Subject: Re: binutils snapshots no longer build gas
Date: Mon, 24 Apr 1995 23:37:00 -0000	[thread overview]
Message-ID: <9504250637.AA35181@sandcastle.watson.ibm.com> (raw)
In-Reply-To: <9504250606.AA05683@cujo.cygnus.com>

	The current state implies that GAS does not build or function at all.
I agree that making GAS the default system assembler may cause some
problems for users, but not building GAS at all seems to be an incorrect
solution at the opposite extreme.  At IBM Watson, I have gas from
binutils-2.5.2 installed as "gas" not "as".  I think the biggest problem
with the current distribution is that this debugging problem is hidden in
a FIXME comment instead of in the GAS documentation for the AIX XCOFF
configuration.  I would let the user/installer decide whether s/he wants
a partially functional GAS instead of implying that no functionality exists.
	Also, AIX XAS has a bug not present in GAS which prevents it from
assembling certain GCC output for the POWER/2 architecture.  XAS incorrectly
exits with an error when it see certain POWER/2 and POWER instructions
utilized in the same assembler source file believing that it is an invalid
combination.

David



  reply	other threads:[~1995-04-24 23:37 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
1995-04-24 23:37       ` David Edelsohn [this message]
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=9504250637.AA35181@sandcastle.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=configure@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=raeburn@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).