From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.2.1?
Date: Fri, 06 Aug 2004 15:10:00 -0000 [thread overview]
Message-ID: <41139F3F.7040508@gnu.org> (raw)
In-Reply-To: <20040805204835.GI1192@gnat.com>
>>What's left for this re-spin?
>>> - ``absolute source path'' patch
>>> - i386 patch
>>> - ?
The MIPS crasher bug is in though. That's the critical one.
> 2 mips-irix patches. You said in one of your earlier message that I
> should feel free to pull in the branch any patch I need for mips-irix.
> I understood that these patches needed to be checked in mainline first
> before they could be integrated in the branch. That's why there not
> in the branch yet.
>
> The first patch was under heavy discussion (about setting the right
> floatformat). I am not where we're headed for this one as I don't have
> the time to work on adding support for IRIX 128bit floats in GDB.
I think it ended with a compromise of a 128-bit IRIX MIPS floatformat.
I'd also like to know the original details on the crash.
> The other one needs to be reworked because Andrew wanted to get some
> reorg done before we looked into this. It's on my plate.
I don't even remember what that one is. Ah, yes, the backtrace fix,
leave that for 6.3.
> What should we do? Push a bit on the resolution of the above 2 patches?
> Or simply pull them in the branch as is, without having checked
> something in head first (this is unorthodox)?
(We've all learnt the hard way to not do this).
So lets get just cover the float bug.
Andrew
next prev parent reply other threads:[~2004-08-06 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:52 Andrew Cagney
2004-08-05 20:13 ` Michael Chastain
2004-08-05 20:48 ` Joel Brobecker
2004-08-06 15:10 ` Andrew Cagney [this message]
2004-08-06 16:16 ` Joel Brobecker
2004-08-07 18:06 ` Andrew Cagney
2004-08-07 18:31 ` Andrew Cagney
2004-08-08 4:00 ` Eli Zaretskii
2004-08-08 12:00 ` Baurjan Ismagulov
2004-08-13 13:50 ` Andrew Cagney
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=41139F3F.7040508@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb@sources.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