From: Kai Tietz <Kai.Tietz@onevision.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Working on the x86_64-windows native port...
Date: Fri, 14 Nov 2008 09:15:00 -0000 [thread overview]
Message-ID: <OF589D8B46.38CD038B-ONC1257501.00320B89-C1257501.0032B436@onevision.de> (raw)
In-Reply-To: <20081113224430.GJ10146@adacore.com>
Hi Joel,
> [ChrisF, I noticed you prefer if we don't Cc you in addition to reaching
> through the mailing-list. I work a little differently, so hopefully
> you'll see this message]
>
> Hello everyone,
>
> Just a quick message to say that I started looking at porting GDB to
> x86_64-windows. Currently, if I use a 32bit compiler and configure
> GDB as a i686-pc-mingw32, I get a fine debugger.
This is really good. I begun with a port of gdb (now about a half a year
ago). If you like I can provide you my work on it. On the other hand, if
you need some support for the x86_64 mingw target in crt, gcc, or
binutils, please let me know.
> [1]: Currently, config.guess (IIRC) doesn't like mingw64. For now,
> I'll keep mingw32 as meaning either 32bit or 64bit. I'll probably
> fix this too, but later.
The mingw64 should be an alias to x86_64-pc-mingw32, nothing more, nothing
less. There were several discussion on that on gcc, and the conclusion was
that the target triplet should be in future on gcc (i?86|x86_64)-pc-mingw.
Best regards,
Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
prev parent reply other threads:[~2008-11-14 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 22:45 Joel Brobecker
2008-11-13 23:00 ` Christopher Faylor
2008-11-15 17:45 ` Joel Brobecker
2008-11-25 17:33 ` Kai Tietz
2008-11-25 19:21 ` Joel Brobecker
2008-11-13 23:08 ` Mark Kettenis
2008-11-14 9:15 ` Kai Tietz [this message]
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=OF589D8B46.38CD038B-ONC1257501.00320B89-C1257501.0032B436@onevision.de \
--to=kai.tietz@onevision.com \
--cc=brobecker@adacore.com \
--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