public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: Eric Christopher <echristo@redhat.com>,
	Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
	Joe Buck <jbuck@synopsys.com>,
	gcc@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: GCC testsuite differences with and without gas on IRIX 6
Date: Wed, 30 Jul 2003 16:59:00 -0000	[thread overview]
Message-ID: <20030730165913.GA27376@redhat.com> (raw)
In-Reply-To: <16165.34417.841407.578041@xayide.TechFak.Uni-Bielefeld.DE>

On Mon, Jul 28, 2003 at 10:24:17PM +0200, Rainer Orth wrote:
> So since nobody seems to see a reason why gas should warn about .space 0,
> what about the following patch then?

Well, the thing is, this is almost certainly a bug in gcc that
it is being emitted in the first place.  I've seen this before
and that has *always* been the case.

I'd prefer that we continue to warn.


r~

  parent reply	other threads:[~2003-07-30 16:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 19:06 Rainer Orth
2003-07-24 19:29 ` Joe Buck
2003-07-24 19:32   ` Eric Christopher
2003-07-24 20:32     ` Thiemo Seufer
2003-07-24 21:46       ` Eric Christopher
2003-07-28 20:24         ` Rainer Orth
2003-07-28 20:32           ` Eric Christopher
2003-07-28 20:36             ` Rainer Orth
2003-07-29 10:43               ` Rainer Orth
2003-07-29 12:34                 ` Thiemo Seufer
2003-07-29 19:59                   ` Eric Christopher
2003-07-29 20:02                     ` Rainer Orth
2003-07-29 20:12                       ` Eric Christopher
2003-07-30 16:59           ` Richard Henderson [this message]
2003-07-30 17:22             ` Rainer Orth
2003-07-30 17:38             ` Eric Christopher

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=20030730165913.GA27376@redhat.com \
    --to=rth@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=echristo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=jbuck@synopsys.com \
    --cc=ro@TechFak.Uni-Bielefeld.DE \
    /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).