From: Eli Zaretskii <eliz@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org
Subject: Re: [RFC] Fix for Go32-v2 native woes
Date: Wed, 07 Apr 2010 06:44:00 -0000 [thread overview]
Message-ID: <E1NzOzi-0004wW-Dz@fencepost.gnu.org> (raw)
In-Reply-To: <i2u6dc9ffc81004062319l66c2045oebce4cc3eb095cb4@mail.gmail.com> (hjl.tools@gmail.com)
> Date: Tue, 6 Apr 2010 23:19:36 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Cc: pierre.muller@ics-cnrs.unistra.fr, gdb-patches@sourceware.org
>
> I have a followup patch on top of AVX gdb to support i386 without
> SSE. I will submit it after AVX patches are checked in.
Thank you.
Btw, what happens with the register-related features you added if
libexpat is not linked in? Do these features silently disappear
(good) or break the build (bad) or cause fatal internal errors at run
time (worse)?
TIA
next prev parent reply other threads:[~2010-04-07 6:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002a01cad517$d36eab90$7a4c02b0$%muller@ics-cnrs.unistra.fr>
[not found] ` <001801cad593$8e70daf0$ab5290d0$%muller@ics-cnrs.unistra.fr>
2010-04-06 17:46 ` Eli Zaretskii
2010-04-06 18:41 ` Mark Kettenis
2010-04-07 3:23 ` Eli Zaretskii
2010-04-07 3:20 ` Eli Zaretskii
2010-04-07 6:19 ` H.J. Lu
2010-04-07 6:44 ` Eli Zaretskii [this message]
2010-04-07 14:41 ` Daniel Jacobowitz
2010-04-07 17:34 ` Eli Zaretskii
2010-04-07 17:37 ` H.J. Lu
2010-04-06 17:48 ` Eli Zaretskii
[not found] <1242886820451223367@unknownmsgid>
2010-04-07 6:32 ` [RFC] Fix for " H.J. Lu
2010-04-07 17:35 ` H.J. Lu
2010-04-07 17:53 ` Eli Zaretskii
2010-04-07 18:01 ` H.J. Lu
[not found] <002a01cad517$d36eab90$7a4c02b0$@muller@ics-cnrs.unistra.fr>
2010-04-06 14:15 ` Pierre Muller
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=E1NzOzi-0004wW-Dz@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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