From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: drow@false.org, Kai.Tietz@onevision.com, gdb@sourceware.org
Subject: Re: Support of gdb for Windows 64 native systems
Date: Fri, 12 Oct 2007 16:51:00 -0000 [thread overview]
Message-ID: <uwstsl1j7.fsf@gnu.org> (raw)
In-Reply-To: <20071012161132.GE4044@adacore.com> (message from Joel Brobecker on Fri, 12 Oct 2007 09:11:32 -0700)
> Date: Fri, 12 Oct 2007 09:11:32 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Daniel Jacobowitz <drow@false.org>, Kai.Tietz@onevision.com,
> gdb@sourceware.org
>
> > Actually, wouldn't it be better to separate the two completely? That
> > should avoid a lot of ugly ifdefs, and make each native backend much
> > cleaner, I think.
>
> The issue with that is that we'll end up duplicating a bit of code.
So what? the duplicates will never be linked into the same build. We
already have duplicate code in targets that are alike, one more cannot
hurt.
In my experience, mixing two different targets is asking for trouble
in the long run.
> In our merge, I counted 5 instances of "ifdef/ifndef __MINGW32__
You need to count "ifdef __CYGWIN__" as well.
> in total, all of them in win32-nat.c:
> - One to define MAXPATHLEN: Should really be done in a proper way,
> so should go away
I don't see this one in the current CVS; am I missing something?
> The rest seems to be in i386-win32-tdep.c which is a separate file.
I don't see this file, either, so I cannot comment on that.
next prev parent reply other threads:[~2007-10-12 16:51 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 [this message]
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
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=uwstsl1j7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Kai.Tietz@onevision.com \
--cc=brobecker@adacore.com \
--cc=drow@false.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