From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'H.J. Lu'" <hjl.tools@gmail.com>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] Prepare for Mingw Windows 64-bit gdbserver
Date: Mon, 19 Apr 2010 14:13:00 -0000 [thread overview]
Message-ID: <000001cadfca$69defe10$3d9cfa30$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <t2j6dc9ffc81004190656o7e697f9xe6d58e3f46999743@mail.gmail.com>
> <pierre.muller@ics-cnrs.unistra.fr> wrote:
> >> > -srv_amd64_regobj="amd64.o x86-64-avx.o"
> >> > +srv_amd64_regobj="amd64.o amd64-avx.o"
> >>
> >> looks like another piece. Is it just a cosmetic change because
> >> we use amd64 instead of x86-64 throughout? Please explain
> >> it and post it separately, if possible.
> >
> > I suspect that this is an error in the commit
> > from H.J. Lu dated 2010/04/07.
> >
> > The ChangeLog says:
> > * configure.srv (srv_i386_regobj): Add i386-avx.o.
> > (srv_i386_linux_regobj): Add i386-avx-linux.o.
> > (srv_amd64_regobj): Add amd64-avx.o.
> >
>
> That was a typo. Thanks for fixing it.
Committed,
Pierre
prev parent reply other threads:[~2010-04-19 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 15:32 [RFC] " Pierre Muller
2010-04-16 15:59 ` Pedro Alves
2010-04-16 16:20 ` Pierre Muller
2010-04-16 16:27 ` Pedro Alves
2010-04-16 16:38 ` Pierre Muller
2010-04-16 17:15 ` Pedro Alves
2010-04-17 5:39 ` [RFA] Use winsock2 for mingw gdbserver Pierre Muller
2010-04-17 8:28 ` Pedro Alves
2010-04-17 20:44 ` Pierre Muller
2010-04-17 5:40 ` [RFC] Mingw Windows 64-bit gdbserver Pierre Muller
2010-04-17 10:58 ` Pedro Alves
2010-04-17 23:18 ` [RFC-v2] " Pierre Muller
2010-04-17 23:46 ` Pedro Alves
2010-04-19 6:37 ` [RFA] Prepare for " Pierre Muller
[not found] ` <6200558430975530197@unknownmsgid>
2010-04-19 13:56 ` H.J. Lu
2010-04-19 14:13 ` Pierre Muller [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='000001cadfca$69defe10$3d9cfa30$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=pedro@codesourcery.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