From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pecarr@linux.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Bug 23438. Support for 128-bit long double types on PowerPC 64]
Date: Tue, 11 Jul 2006 22:59:00 -0000 [thread overview]
Message-ID: <200607112259.k6BMxWae016835@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <44B42374.1000109@linux.ibm.com> (message from Pete Carr on Tue, 11 Jul 2006 15:17:24 -0700)
> Date: Tue, 11 Jul 2006 15:17:24 -0700
> From: Pete Carr <pecarr@linux.ibm.com>
>
> Hi,
Hi Pete, Welcome to GDB.
> Please note that there are changes to floatformat.h and floatformat.c which
> are held under include and libiberty subdirectories.
Those bits need to be handled seperately; see the toplevel MAINTAINERS
file for details.
> This is my first patch submission so I'd appreciate guidance if I have
> not followed the rules.
You'll need to work a bit on your coding style ;-). I noticed that
your lines tend to be too long (there's some debate what the maximum
length is, but they definitely should be under 79 characters), and you
comments are no formatted correctly. Please take some time to read
the GNU coding standards; feel free to ask any questions that remain
after doing that.
As for the patch, the change to rs6000-tdep.c is almost certainly
wrong, since it also seems to affect 32-bit powerpc and POWER stuff.
Regarding the ppc-linux-tdep.c change: we generally don't #ifdef out
code, but just remove it, since CVS tracks the history for us. But
again, I don't think this change is right, since the code is also for
32-bit powerpc support. And even for powerpc64, there still are
systems out there that use the old ABI with 64-bit long doubles isn't
it? How does this change affect those systems?
Mark
next prev parent reply other threads:[~2006-07-11 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 22:17 Pete Carr
2006-07-11 22:59 ` Mark Kettenis [this message]
2006-07-12 3:51 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 16:44 Pete Carr
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=200607112259.k6BMxWae016835@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=pecarr@linux.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