From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Tristan Gingold <gingold@adacore.com>, gdb@sourceware.org
Subject: Re: gdb cvs vs x86_64-apple-darwin10
Date: Mon, 31 Aug 2009 13:33:00 -0000 [thread overview]
Message-ID: <7BDB0E6F-A184-4161-BA70-99353F83B3EF@elis.ugent.be> (raw)
In-Reply-To: <20090831132221.GC10965@bromo.med.uc.edu>
On 31 Aug 2009, at 15:22, Jack Howarth wrote:
> Getting x86_64-apple-darwin10 working should be a higher priority
> for gdb 7.0 since it sounds like after the VTA branch merge into gcc
> 4.5, we will need to have access to gdb 7.0 to debug code generated
> with gcc 4.5 on darwin
Do you think Apple will ever ship anything >gcc 4.2 on Mac OS X? As
far as I can tell, they are trying to move completely to Clang+LLVM.
Of course, maybe you build your own gcc (and AdaCore most certainly
does build its own gcc).
Jonas
next prev parent reply other threads:[~2009-08-31 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 7:58 Jack Howarth
2009-08-31 13:10 ` Tristan Gingold
2009-08-31 13:29 ` Jack Howarth
2009-08-31 13:33 ` Jonas Maebe [this message]
2009-08-31 16:38 ` Jack Howarth
2009-08-31 16:20 ` Tristan Gingold
2009-08-31 18:11 ` Jack Howarth
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=7BDB0E6F-A184-4161-BA70-99353F83B3EF@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=howarth@bromo.med.uc.edu \
/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