From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Subject: Re: [commit] 128-bit long double for mips64-linux
Date: Wed, 15 Mar 2006 23:45:00 -0000 [thread overview]
Message-ID: <200603152300.k2FN0lDS017750@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060315224432.GA25757@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 15 Mar 2006 17:44:32 -0500)
> Date: Wed, 15 Mar 2006 17:44:32 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, Mar 15, 2006 at 11:39:53PM +0100, Mark Kettenis wrote:
> > What's up with the mips-tdep.c change? Your ChangeLog doesn't mention
> > it, but it seems you committed it.
>
> Oops! Here's what happened:
>
> > > 2006-03-15 Daniel Jacobowitz <dan@codesourcery.com>
> > >
> > > * mips-linux-tdep.c: Include "floatformat.h".
> > > (mips_linux_init_abi): Use 128-bit long double for N32 and N64.
>
> Insert "* mips-tdep.c " at the beginning of the next line:
>
> > > (mips_n32n64_return_value): Support 128-bit long double.
> > > (print_gp_register_row): Don't print spaces before ignored
> > > or floating point registers.
>
> Real sorry about that, I've fixed the ChangeLog. That caused bizarre
> stray whitespace to appear in the output of "info reg" on MIPS.
>
> I also missed this:
>
> * Makefile.in (mips-linux-tdep.o): Update.
>
> Too many changelog entries in one day, I guess.
No problem. Thanks for fixing it.
Mark
prev parent reply other threads:[~2006-03-15 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 17:01 Daniel Jacobowitz
2006-03-15 23:00 ` Mark Kettenis
2006-03-15 23:04 ` Daniel Jacobowitz
2006-03-15 23:45 ` Mark Kettenis [this message]
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=200603152300.k2FN0lDS017750@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
/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