Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com,  Kai.Tietz@onevision.com,  gdb@sourceware.org
Subject: Re: Support of gdb for Windows 64 native systems
Date: Sat, 13 Oct 2007 19:19:00 -0000	[thread overview]
Message-ID: <47111A25.2020402@portugalmail.pt> (raw)
In-Reply-To: <uzlymkf1p.fsf@gnu.org>

Eli Zaretskii wrote:

>> I propose goind the other way around.  Start by adding the needed configury
>> bits needed, a mingw.mt file, and disabling the cygwin specific bits in
>> win32-nat.c around #ifdef __CYGWIN__ blocks.  I'd like to keep the
>> changes mostly in sync with gdbserver/win32-low.c too, but that shouldn't
>> be a priority.  We can then peacewise enhance the mingw port and bring
>> its features up.
> 
> We don't need to go that slow.
> 

Sure, but it's the natural way to introduce the new target.  I'm not saying
it should be done slowly timewise.  I'm saying it should start from the
bottom up patchwise.  It can be submitted in a patch series in the
same minute for all I care.  The point is, we shouldn't be looking at
a patch and deciding what we *don't* need; we should be looking at
what we have, and deciding what we *do* need.

-- 
Cheers,
Pedro Alves


  reply	other threads:[~2007-10-13 19:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071011142348.GA18239@caradoc.them.org>
2007-10-11 14:47 ` Kai Tietz
     [not found]   ` <20071011145549.GA19918@caradoc.them.org>
2007-10-11 16:01     ` Joel Brobecker
2007-10-12  3:38       ` Christopher Faylor
2007-10-12  4:27         ` Joel Brobecker
2007-10-11 16:37     ` Mark Kettenis
2007-10-12  7:19     ` Kai Tietz
2007-10-12  8:44     ` Eli Zaretskii
2007-10-12 16:11       ` Joel Brobecker
2007-10-12 16:51         ` Eli Zaretskii
2007-10-12 17:45           ` Joel Brobecker
2007-10-12 20:29             ` Eli Zaretskii
2007-10-12 22:28               ` Joel Brobecker
2007-10-13  2:41                 ` Joel Brobecker
2007-10-13 10:48                   ` Eli Zaretskii
2007-10-13 15:47                     ` Joel Brobecker
2007-10-13 17:05                       ` Christopher Faylor
2007-10-13 17:36                       ` Pedro Alves
2007-10-13 19:09                         ` Eli Zaretskii
2007-10-13 19:19                           ` Pedro Alves [this message]
2007-10-13 20:51                         ` Joel Brobecker
2007-10-13 22:52                           ` Pedro Alves
2007-10-14  5:16                             ` Joel Brobecker
2007-10-14 11:44                               ` Pedro Alves
2007-10-14 20:33                                 ` Eli Zaretskii
2007-10-12 17:38         ` Pedro Alves
2007-10-11 13:53 Kai Tietz
2007-10-11 14:05 ` Daniel Jacobowitz
2007-10-11 14:18   ` Kai Tietz

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=47111A25.2020402@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=Kai.Tietz@onevision.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    /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