From: Pedro Alves <palves@redhat.com>
To: Andreas Tobler <andreast-list@fgznet.ch>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] FreeBSD powerpc support
Date: Tue, 11 Dec 2012 20:07:00 -0000 [thread overview]
Message-ID: <50C79283.1050608@redhat.com> (raw)
In-Reply-To: <50B4FC29.9050006@fgznet.ch>
On 11/27/2012 05:45 PM, Andreas Tobler wrote:
>> - If the function implements of a target/gdbarch/etc. method, then
>> comment it as such. E.g.,
>>
>> /* This is the implementation of gdbarch method FOOBAR. */
>>
>> - I noticed some functions with long comments are copies of existing
>> code of other ports. I wonder if we could perhaps share more code.
>
> True, here I do not know how to share, maybe a common ppc64-tdep-common.c?
The tdep files are usually called ARCH-OS-tdep.c, so that would be
ppc64-common-tdep.c. That raises the question of what's different between
ppc64-common-tdep.c and ppc64-tdep.c. Clearer alternatives could be
ppc64-unix-tdep.c or some other token that describes the commonality between
what's being shared (as opposed to just the fact that something is shared,
as in "common"). In any case, the name of the file is the minor detail.
>> read_memory_unsigned_integer nowadays has a byte_order parameter,
>> so just pass it BFD_ENDIAN_BIG, and you're set.
>
> Done. Even tested on ppc64-linux. I might send a patch for
> ppc-linux-tdep.c as well. Likewise for the below.
That'd be nice.
>> For some reason this bailing out if name is not null jumped at me.
>> It's not obvious to me what that means, so it felt like it deserves
>> a comment.
>
> Also done, I hope I match the expectations.
You have, thanks.
>
>> On 11/19/2012 09:43 PM, Andreas Tobler wrote:
>>> --- configure.host 30 May 2012 19:41:34 -0000 1.107
>>> +++ configure.host 19 Nov 2012 21:24:15 -0000
>>> @@ -125,6 +125,7 @@
>>>
>>> powerpc-*-aix* | rs6000-*-*)
>>> gdb_host=aix ;;
>>> +powerpc*-*-freebsd*) gdb_host=fbsd ;;
>>
>> This seems to be 'powerpc-*-freebsd*' elsewhere I looked (top level, bfd).
>> Why the extra wildcard?
>
>
> Hm, here I'm not sure. My targets report as powerpc-unknown-freebsd*
> (32-bit) and powerpc64-unknown-freebsd* (64-bit). So I thought I have to
> match both. Is this not correct?
I guess that's fine then.
> Attached a revised version of the diff.
Thanks. Please always paste the ChangeLog entry along with the patch
too, even if it hadn't needed changes.
> +#include "features/rs6000/powerpc-32l.c"
> +#include "features/rs6000/powerpc-64l.c"
This is a problem. I notice you have tdesc related things in your patch,
but nothing is actually making use of the target descriptions -- neither
the core support, nor the native debugger support code is implementing
the "return target's target description" hooks. Furthermore, you're
using the target descriptions and calling the same initialization
functions that ppc-linux-tdep.c calls. Please try an --enable-targets=all
build -- I'm guessing you'll see multiple-definition link errors.
--
Pedro Alves
next prev parent reply other threads:[~2012-12-11 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 21:44 Andreas Tobler
2012-11-23 19:34 ` Pedro Alves
2012-11-27 17:45 ` Andreas Tobler
2012-12-11 15:48 ` PING " Andreas Tobler
2012-12-11 16:14 ` Pedro Alves
2012-12-11 16:33 ` Andreas Tobler
2012-12-11 20:07 ` Pedro Alves [this message]
2012-12-12 20:07 ` Andreas Tobler
2012-12-13 20:04 ` Pedro Alves
2012-12-13 20:20 ` Andreas Tobler
2012-12-13 20:27 ` Pedro Alves
2012-12-13 20:35 ` Andreas Tobler
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=50C79283.1050608@redhat.com \
--to=palves@redhat.com \
--cc=andreast-list@fgznet.ch \
--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