public inbox for gdb@sourceware.org
 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: Sun, 06 Jan 2013 00:26:00 -0000	[thread overview]
Message-ID: <CAGWvnymTd7u_PfOQx2V1G2KsnmPBHdG=PY6fv__e-obPzVm2YA@mail.gmail.com> (raw)
In-Reply-To: <20130105145213.GK3567@adacore.com>

On Sat, Jan 5, 2013 at 9:52 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> It does not look like the changes were merged into the FSF tree.  This
>> also does not support some of the more recent AIX features added to
>> GCC.
>
> Tristan is usually pretty good at sending these sorts of patches.
> I will ask him on Monday if some might be missing. He's been
> extremely busy lately, so it's a possibility. It would also be
> useful to explain how you are basing your evaluation, and in
> particular say what does not work for you.

I and others have not been able to use GNU as and GNU ld to bootstrap
GCC. The resulting object files and shared objects mostly worked in
small experiments, but failed for larger projects, like GCC.

Also, GNU as and GNU ld do not contain support for the new
cmodel=large and thread local storage support added to GCC.

- David

  reply	other threads:[~2013-01-06  0:26 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 [this message]
2013-01-06  7:00                   ` Joel Brobecker
2013-01-08  8:10                     ` Joel Brobecker
2013-01-08 14:38                       ` David Edelsohn
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='CAGWvnymTd7u_PfOQx2V1G2KsnmPBHdG=PY6fv__e-obPzVm2YA@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).