Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Properly define SSE registers for cygwin targets
Date: Sun, 14 Sep 2003 17:35:00 -0000	[thread overview]
Message-ID: <20030914173526.GA26986@redhat.com> (raw)
In-Reply-To: <200309141546.h8EFkjeO015098@elgar.kettenis.dyndns.org>

On Sun, Sep 14, 2003 at 05:46:45PM +0200, Mark Kettenis wrote:
>   Date: Sat, 13 Sep 2003 11:51:57 -0400
>   From: Christopher Faylor <cgf@redhat.com>
>
>   Another question:  If HAVE_SSE_REGS was eliminated from all source files
>   why wasn't it eliminated from win32-nat.c?  Did I miss a memo?
>
>Well, I'm pretty sure I've burried a comment about Cygwin still using
>HAVE_SSE_REGS somewhere in a comment of one of the zillion
>i386-specific patches over the last year.  Do you want me to drop you
>a note if something Cygwin-specific comes up?

Hmm.  I usually scan the gdb-patches and gdb mailing lists for the cygwin
keyword but I probably missed this.

I appreciate the offer but I'll just try to make sure that I do better in
the future.  There's no need for you to go to extra effort.  Although,
if you notice something that requires an obvious fix in win32-nat.c, or
whatever, then feel free to check it in (maybe you're doing that
already).  I'll be on the lookout for that too so that I can test
changes that impact cygwin.

cgf


  reply	other threads:[~2003-09-14 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13  2:28 Christopher Faylor
2003-09-13 11:03 ` Mark Kettenis
2003-09-13 15:52   ` Christopher Faylor
2003-09-13 16:04     ` Christopher Faylor
2003-09-14 15:46     ` Mark Kettenis
2003-09-14 17:35       ` Christopher Faylor [this message]
2003-09-13 17:02 ` [PATCH] Make SSE registers unconditionally available on cygwin Christopher Faylor

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=20030914173526.GA26986@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.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