Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: amodra@bigpond.net.au (Alan Modra),
	Ulrich.Weigand@de.ibm.com,
	        gdb-patches@sources.redhat.com
Subject: Re: [patch] dw2-ranges.S non-g GAS crash  [Re: spu-as internal error]
Date: Tue, 08 Apr 2008 05:42:00 -0000	[thread overview]
Message-ID: <200804072256.m37MuAcM023193@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080407063027.GA26788@host0.dyn.jankratochvil.net> from "Jan Kratochvil" at Apr 07, 2008 08:30:27 AM

Jan Kratochvil wrote:

> > Has this testcase ever assembled?  On any target?  I think gas would
> > always have aborted unless you pass -g to gas or supply .file
> > directives.
> 
> It was always built just inside `runtest'.
> 
> Requesting a commit approval.  Verified unpatched GDB still FAILs on it.

As I just noticed, this is really also a spu-gcc problem: gcc *is* always
called with -g, but spu-gcc does not pass this on to the assembler.

Do you still think we should add the .file directive, or does the test
case make more sense without it?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-04-07 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF789B1703.6C47E7DB-ONCA257424.0010854A-E9257424.00108D3E@au1.ibm.com>
     [not found] ` <20080407040340.GF1446@bubble.grove.modra.org>
2008-04-07 11:47   ` Jan Kratochvil
2008-04-08  5:42     ` Ulrich Weigand [this message]
2008-04-08  7:56       ` Jan Kratochvil
2008-04-14 19:08     ` Daniel Jacobowitz

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=200804072256.m37MuAcM023193@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=amodra@bigpond.net.au \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jan.kratochvil@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