Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Prec x86 MMX 3DNow! SSE SSE2 SSE3 SSSE3 SSE4 support
Date: Fri, 18 Dec 2009 19:44:00 -0000	[thread overview]
Message-ID: <4B2BDAEC.7090207@vmware.com> (raw)
In-Reply-To: <daef60380912141746i1325610fp1ede9eeacc28c209@mail.gmail.com>

Sounds like this patch waits only for new test suites?

Hui Zhu wrote:
> http://sourceware.org/ml/gdb/2009-10/msg00414.html
> 
> this bug just reproduce in amd64 ubuntu 9.0.4 and i386 ubuntu 9.0.4
> that's gcc is 4.3.3. glibc is 2.9.
> 
> In amd64 gcc 4.1.2 glibc 2.5 and i386 gcc 4.2.4 glibc 2.7, it cannot
> be reproduced.
> 
> I think this is a bug in corelow or gcore.
> 
> Thanks,
> Hui
> 
> On Tue, Dec 15, 2009 at 02:22, Michael Snyder <msnyder@vmware.com> wrote:
>> Hui Zhu wrote:
>>
>>> solib-precsave.exp, this fail is because the core solib error that I
>>> report in before.
>> Can you say more about that?
>>
>> I don't remember it, and it never fails for me (before or after
>> this patch).
>>
>>
> 


  reply	other threads:[~2009-12-18 19:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 15:00 Hui Zhu
2009-12-07 16:54 ` Michael Snyder
2009-12-07 17:16 ` Michael Snyder
2009-12-07 17:43   ` Joel Brobecker
2009-12-07 17:54     ` Michael Snyder
2009-12-07 18:00       ` Joel Brobecker
2009-12-07 18:05         ` Michael Snyder
2009-12-08  5:51           ` Hui Zhu
2009-12-08 19:56             ` Michael Snyder
2009-12-07 18:08         ` Doug Evans
2009-12-08 17:43         ` Tom Tromey
2009-12-10 19:52 ` Michael Snyder
2009-12-11 15:00   ` Hui Zhu
2009-12-13  4:28     ` Hui Zhu
2009-12-13 10:35       ` Hui Zhu
2009-12-14 18:24       ` Michael Snyder
2009-12-15  1:47         ` Hui Zhu
2009-12-18 19:44           ` Michael Snyder [this message]
2010-01-08 16:07             ` Hui Zhu
2010-01-08 18:45               ` Michael Snyder
2010-01-09 12:28               ` [RFA/i386] " Joel Brobecker
2010-01-11  2:48                 ` Hui Zhu
2010-01-11  4:05                   ` Joel Brobecker
2010-01-12  1:38                   ` Michael Snyder
2010-03-28 16:27                     ` Hui Zhu
2010-03-29  1:35                       ` Michael Snyder
2010-03-29  1:36                       ` Michael Snyder
2010-03-29  9:25                         ` Hui Zhu
2010-03-29  1:40                       ` Michael Snyder
2010-03-29  2:23                         ` Hui Zhu
2010-03-29 13:21                           ` Hui Zhu
2010-03-29 17:52                             ` Michael Snyder
2010-03-29 18:11                             ` Michael Snyder
2010-03-30  6:29                               ` Hui Zhu
2010-03-30 12:55                                 ` Hui Zhu
2010-04-01 15:36                                   ` Hui Zhu
2010-04-01 21:50                                     ` Michael Snyder
2010-04-02  5:14                                       ` Hui Zhu
2010-03-29  2:18                       ` Michael Snyder

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=4B2BDAEC.7090207@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.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