From: Michael Snyder <msnyder@vmware.com>
To: Andreas Tobler <andreast-list@fgznet.ch>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] FreeBSD powerpc (32-bit) support
Date: Mon, 31 Jan 2011 21:38:00 -0000 [thread overview]
Message-ID: <4D4721B2.3080606@vmware.com> (raw)
In-Reply-To: <4D471E05.9090307@fgznet.ch>
Andreas Tobler wrote:
> Hi all,
>
> the attached patch adds support for FreeBSD PowerPC, 32-bit.
> It is derived from ppcobsd* with FreeBSD additions.
>
> Currently missing/incomplete:
> - Altivec support, I need to implement the necessary kernel bits first.
> - HW watchpoints, also kernel bits are missing.
> - full thread support.
> - some sig tests.
>
> The test suite run from yesterday gave the below summary:
>
> === gdb Summary ===
>
> # of expected passes 14148
> # of unexpected failures 371
> # of expected failures 67
> # of untested testcases 34
> # of unsupported tests 87
>
> As of today I'm not able to build with python support. Need to figure
> out why. I guess the latest configure(.ac) does not like my output.
> (-L/usr/local/lib/python2.6/config -lutil -lm -lpython2.6
> -Wl,--export-dynamic)
>
> No, I do not have a gdb assignment yet. Tom already sent me the form and
> I'll complete it soon.
>
>
> I'd appreciate comments and corrections.
>
> TIA,
> Andreas
>
> Below the ChangeLog:
>
> 2011-01-31 Andreas Tobler <andreast@fgznet.ch>
>
> * Makefile.in (ALL_TARGET_OBS): Add powerpc FreeBSD files.
> * configure.host: Add powerpc-*-freebsd* target.
> * configure.tgt: Add target info for powerpc-*-freebsd*.
> * ppcfbsd-nat.c, ppcfbsd-tdep.h, ppcfbsd-tdep.c: New files.
> * config/powerpc/fbsd.mh: New file.
Looks nice at a first glance.
Nit: mis-indented here:
+ ppc_supply_gregset (&ppcfbsd_gregset, regcache, regno,
+ ®s, sizeof regs);
prev parent reply other threads:[~2011-01-31 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 20:55 Andreas Tobler
2011-01-31 21:38 ` Michael Snyder [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=4D4721B2.3080606@vmware.com \
--to=msnyder@vmware.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