Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Jonas Maebe <jonas.maebe@elis.ugent.be>
Cc: Tristan Gingold <gingold@adacore.com>, gdb@sourceware.org
Subject: Re: gdb cvs vs x86_64-apple-darwin10
Date: Mon, 31 Aug 2009 16:38:00 -0000	[thread overview]
Message-ID: <20090831163358.GA12873@bromo.med.uc.edu> (raw)
In-Reply-To: <7BDB0E6F-A184-4161-BA70-99353F83B3EF@elis.ugent.be>

On Mon, Aug 31, 2009 at 03:29:11PM +0200, Jonas Maebe wrote:
>
> 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

Jonas,
   No. I strongly doubt Apple will ever ship a gcc > 4.2.1 due to a combination
of their objections to GPLv3 and their preception that gcc has been treading
water in terms of improvements. As the FSF gcc developers are fond of saying,
it's hard to make the elephant dance so Apple wanted to start with a more
modern code base and design with clang/llvm. FYI, I maintain the gcc packages for
fink and so far we have had pretty good luck with FSF gcc maintaining quality...

http://gcc.gnu.org/ml/gcc-testresults/2009-07/msg01866.html

although there will be forks coming like with LTO. Apple wants to use a
different approach for implementing LTO than FSF gcc does. I was told by
the llvm folks...

> The FSF is designing their LTO to not need linker integration.  This
> will present a whole host of problems for them, but they are insistent
> on it.  :)

I am unclear if the FSF design could be adapted for darwin without Apple's
participation on the linker side.
                  Jack


  reply	other threads:[~2009-08-31 16:34 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
2009-08-31 16:38       ` Jack Howarth [this message]
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=20090831163358.GA12873@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=jonas.maebe@elis.ugent.be \
    /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