From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: PR corefiles/11481: gcore doesn't work on i386 without SSE
Date: Fri, 09 Apr 2010 20:08:00 -0000 [thread overview]
Message-ID: <t2x6dc9ffc81004091308v63a09220rf211f0b4687eb30@mail.gmail.com> (raw)
In-Reply-To: <201004091915.o39JFfFN011160@glazunov.sibelius.xs4all.nl>
On Fri, Apr 9, 2010 at 12:15 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Fri, 9 Apr 2010 09:01:01 -0700
>> From: "H.J. Lu" <hjl.tools@gmail.com>
>>
>> On Fri, Apr 9, 2010 at 8:59 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> >> Date: Fri, 9 Apr 2010 08:50:12 -0700
>> >> From: "H.J. Lu" <hongjiu.lu@intel.com>
>> >>
>> >> Hi,
>> >>
>> >> This patch fixes gcore by not generating core regset sections which
>> >> aren't supported by i386 without SSE. OK to install?
>> >
>> > Sorry, I think this is the wrong way to fix this.
>> >
>>
>> Any suggestions?
>
> Yup. This makes sure we always install a list of register notes that
> matches the target description.
>
> 2010-04-09 Mark Kettenis <kettenis@gnu.org>
>
> * i386-linux-tdep.c (i386_linux_regset_sections): Remove extended
> register note sections.
> (i386_linux_sse_regset_sections, i386_linux_avx_regset_sections):
> New variables.
> (i386_linux_init_abi): Install list of supported register note
> sections that matches the target description.
>
That is nice. We should do the same thing in amd64-linux-tdep.c.
Thanks.
--
H.J.
next prev parent reply other threads:[~2010-04-09 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 15:50 H.J. Lu
2010-04-09 16:00 ` Mark Kettenis
2010-04-09 16:01 ` H.J. Lu
2010-04-09 19:15 ` Mark Kettenis
2010-04-09 20:08 ` H.J. Lu [this message]
2010-04-09 20:43 ` H.J. Lu
2010-04-10 14:49 ` Mark Kettenis
2010-04-10 15:46 ` H.J. Lu
2010-04-13 21:39 ` Mark Kettenis
2010-04-13 21:50 ` Pedro Alves
2010-04-09 16:02 ` Joel Brobecker
2010-04-09 16:05 ` H.J. Lu
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=t2x6dc9ffc81004091308v63a09220rf211f0b4687eb30@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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