From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [patch] KFAIL gdb/1025
Date: Tue, 04 Feb 2003 22:28:00 -0000 [thread overview]
Message-ID: <ro18ywv3cks.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro13cn455km.fsf@jackfruit.Stanford.EDU>
On 04 Feb 2003 09:16:57 -0800, David Carlton <carlton@math.Stanford.EDU> said:
> Anyways, I'll upgrade my binutils when I have some free time (probably
> this afternoon) and see how that affects matters.
Okay, I've upgraded binutils to 2.13.2.1; these failures go away,
along with failures on several other tests. (Though the down side is
that I can't compile all the programs in gdb.java now; a pity, but
I'll survive.)
But I do see the failures that Michael reports with GCC 2.95.3
combined with DWARF 2. (In other words, failures on the tests that
are smaller than ints, though not the double failure that I had been
seeing with the old binutils.) So I'm leaving the PR open for now; if
we ever figure out what's up with that, we can close the PR and/or
XFAIL the tests, as appropriate.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-02-04 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 1:18 David Carlton
2003-02-04 14:44 ` Daniel Jacobowitz
2003-02-04 17:17 ` David Carlton
2003-02-04 17:22 ` Daniel Jacobowitz
2003-02-04 22:28 ` David Carlton [this message]
2003-02-06 20:59 ` David Carlton
2003-02-04 15:32 Michael Elizabeth Chastain
2003-02-04 18:33 Michael Elizabeth Chastain
2003-02-04 20:07 Michael Elizabeth Chastain
2003-02-05 6:04 Michael Elizabeth Chastain
2003-02-07 16:16 Michael Elizabeth Chastain
2003-02-07 17:04 ` David Carlton
2003-02-07 17:08 Michael Elizabeth Chastain
2003-02-07 17:13 ` David Carlton
2003-02-07 17:40 Michael Elizabeth Chastain
2003-02-07 17:46 ` David Carlton
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=ro18ywv3cks.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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