From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] move sparc-sol-thread.c back into sol-thread.c.
Date: Fri, 10 May 2013 11:10:00 -0000 [thread overview]
Message-ID: <yddd2sz9jkp.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <1367842203-31747-1-git-send-email-brobecker@adacore.com> (Joel Brobecker's message of "Mon, 6 May 2013 08:10:03 -0400")
Hi Joel,
> Contrary to what the man page says, the routines in sparc-sol-thread
> are needed on some non-SPARC systems, more precisly on x86_64.
> So this patch deletes sparc-sol-thread.c and moves the code back
> inside sol-thread.c, with some added comments warning the reader
> about this pitfall.
I've done some digging and found that xregs on Solaris/amd64 were added
for AVX support, in Solaris 10 Update 10 apparently:
http://www.mail-archive.com/opensolaris-arc@opensolaris.org/msg01454.html
As we already found, whether or not you find ps_lgetxregsize documented
as SPARC-specific depends on the version of the Solaris 10 man pages you
are looking at, and in S11 it has been there from the beginning. So
please adapt the comments accordingly, or even leave out the x86_64
reference altogether.
> gdb/ChangeLog:
>
> PR tdep/15420:
> * sol-thread.c (ps_lgetxregsize, ps_lgetxregs, ps_lsetxregs):
> New functions, directly copied from sparc-sol-thread.c.
> * sparc-sol-thread.c: Delete.
> * configure.ac: Remove code handling sparc-solaris-thread.c.
> * configure: Regenerate.
>
> Tested on sparc-solaris. Rainer, would you mind confirming that this
> fixes your problem as well?
I've removed my configure hack to use sparc-sol-thread.c everywhere,
applied your patch and rebuilt gdb: it works just fine now.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2013-05-10 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 12:10 Joel Brobecker
2013-05-10 11:10 ` Rainer Orth [this message]
2013-05-10 12:12 ` Joel Brobecker
2013-05-10 12:23 ` Rainer Orth
2013-05-10 12:33 ` cheked in (7.6): " Joel Brobecker
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=yddd2sz9jkp.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=brobecker@adacore.com \
--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