This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Fix for Go32-v2 native woes
- From: Eli Zaretskii <eliz at gnu dot org>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: pierre dot muller at ics-cnrs dot unistra dot fr, gdb-patches at sourceware dot org
- Date: Wed, 07 Apr 2010 02:44:10 -0400
- Subject: Re: [RFC] Fix for Go32-v2 native woes
- References: <002a01cad517$d36eab90$7a4c02b0$%muller@ics-cnrs.unistra.fr> <001801cad593$8e70daf0$ab5290d0$%muller@ics-cnrs.unistra.fr> <83iq84xyoa.fsf@gnu.org> <83y6h0vtj6.fsf@gnu.org> <i2u6dc9ffc81004062319l66c2045oebce4cc3eb095cb4@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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