From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Alan Modra <amodra@bigpond.net.au>,
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 07:56:00 -0000 [thread overview]
Message-ID: <20080407230222.GA590@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <200804072256.m37MuAcM023193@d12av02.megacenter.de.ibm.com>
On Tue, 08 Apr 2008 00:56:10 +0200, Ulrich Weigand wrote:
> 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.
...
> Do you still think we should add the .file directive, or does the test
> case make more sense without it?
I think it is not nice the testcase fails to build without `-g' due to an
internal error of GAS. I was not aware of it.
It is goot to know it is no longer required to be committed.
I requested the approval if it cannot conflict in some way with the debug info
being generated with `-g' but I doubt so.
Regards,
Jan
next prev parent reply other threads:[~2008-04-07 23:02 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
2008-04-08 7:56 ` Jan Kratochvil [this message]
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=20080407230222.GA590@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=amodra@bigpond.net.au \
--cc=gdb-patches@sources.redhat.com \
--cc=uweigand@de.ibm.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