Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, David Taylor <dtaylor@emc.com>,
	binutils@sourceware.org, 	gcc@gcc.gnu.org, gdb@sourceware.org
Subject: Re: stabs support in binutils, gcc, and gdb
Date: Tue, 08 Jan 2013 14:38:00 -0000	[thread overview]
Message-ID: <CAGWvny=T8Pwyf9jZT=TgNGXAtsXUpgQUzO+qiOVfP3mbOgZ0uQ@mail.gmail.com> (raw)
In-Reply-To: <20130108081042.GR3567@adacore.com>

On Tue, Jan 8, 2013 at 3:10 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> I was able to speak to Tristan, yesterday, and he confirmed that
> we haven't been able to contribute a few of the patches he wrote.
> Unfortunately, his TODO list is more than full, at the moment, and
> we don't think he'll have time to work on that for a while. I might
> have time in the next few weeks to track them down - if I do, I will
> post them.
>
> With all patches, we are able to bootstrap GCC 4.7. But we haven't
> tried the HEAD version. From David's report, it sounds like we should
> expect additional work if we want to do it.

It would be helpful for Adacore to contribute the support upstream
into the FSF tree, not only to make GNU Binutils more useful on AIX
but to avoid others duplicating your work -- especially in
incompatible ways.

The large TOC feature (cmodel=large) is not used by default and the
TLS feature is not enabled by default, so HEAD probably should
bootstrap with your private changes to Binutils. TLS tests for
assembler support, so that should fail with Binutils.

I had wanted your feedback about TLS within Ada before enabling the
configuration test by default, but that apparently will not be
possible with the way that Adacore's development model on AIX has
diverged.

Thanks, David


  reply	other threads:[~2013-01-08 14:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12972.1357230104__33958.3243280233$1357230256$gmane$org@usendtaylorx2l>
2013-01-03 17:02 ` Tom Tromey
2013-01-03 20:53   ` David Edelsohn
2013-01-03 21:53     ` Jonas Maebe
2013-01-03 22:02       ` David Edelsohn
2013-01-04  4:12     ` Joel Brobecker
2013-01-04 20:20       ` David Edelsohn
2013-01-05  0:11         ` David Edelsohn
2013-01-05  7:53           ` Joel Brobecker
2013-01-05 13:28             ` David Edelsohn
2013-01-05 14:52               ` Joel Brobecker
2013-01-06  0:26                 ` David Edelsohn
2013-01-06  7:00                   ` Joel Brobecker
2013-01-08  8:10                     ` Joel Brobecker
2013-01-08 14:38                       ` David Edelsohn [this message]
2013-01-08 14:46                         ` Arnaud Charlet
2013-01-08 14:49                           ` David Edelsohn
2013-01-08 14:58                             ` Arnaud Charlet
2013-01-03 16:22 David Taylor
2013-01-03 16:42 ` Richard Biener
2013-01-03 16:53 ` Joel Brobecker
2013-01-03 16:56 ` nick clifton
2013-01-04  3:31   ` Doug Evans
2013-01-11 14:53     ` David Taylor
2013-01-11 17:41       ` Doug Evans
2013-01-12  1:55         ` Cary Coutant
2013-01-12  2:17           ` Ian Lance Taylor
2013-01-14 16:06             ` Doug Evans
2013-01-14 19:45             ` Cary Coutant
2013-01-14 16:12           ` Doug Evans
2013-01-14 19:49             ` Jan Kratochvil
2013-01-12 13:26       ` Andreas Schwab
2013-01-14 18:57         ` David Taylor
2013-01-14 22:18           ` Andreas Schwab
2013-01-14 23:41             ` Eric Botcazou

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='CAGWvny=T8Pwyf9jZT=TgNGXAtsXUpgQUzO+qiOVfP3mbOgZ0uQ@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=dtaylor@emc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /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