public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jeff Law <law@redhat.com>,
		John David Anglin <danglin@gcc.gnu.org>,
	rupp@gnat.com, 	"Joseph S. Myers" <joseph@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Temporarily revert Steven's PCH changes for 4.8 (PR pch/54117)
Date: Thu, 14 Feb 2013 11:27:00 -0000	[thread overview]
Message-ID: <CABu31nO_wThtZnKY6bnr47b9DyqABEvXbggit-o-amHaErv7Qw@mail.gmail.com> (raw)
In-Reply-To: <CAGWvny=R6EwTL8wVKq8Cjp6Y79uOE0pshNT=OJ1vnxhmFaMNrw@mail.gmail.com>

On Wed, Feb 13, 2013 at 10:33 PM, David Edelsohn wrote:
> The AIX system supports DWARF debugging, but GCC does not generate it
> on AIX and GDB does not consume it on AIX.

Is there a description for what has to be done in GCC to enable DWARF
with AIX as/ld? E.g. is it required to support the ".dwsect" pseudo?
Is there already a plan from someone to make GCC produce DWARF on
AIX7?

AFAICT, for gcc+gas it should already work with binutils that include
the AdaCore patch for DWARF support. But this has apparently not been
tested with AIX ld, and there are AdaCore local patches pending.
http://sourceware.org/ml/binutils/2011-04/msg00250.html
http://www.sourceware.org/ml/gdb/2013-01/msg00030.html


> If you want to disable PCH on STABS systems on just AIX, that is fine.

This is probably what we'll end up doing, one way or another. That's
good enough for the goals I'm trying to achieve in the short term
(which means up to 2 years in my case ;-).

Ciao!
Steven

  parent reply	other threads:[~2013-02-14 11:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 15:54 Jakub Jelinek
2013-02-13 18:23 ` Jeff Law
2013-02-13 20:07   ` Jakub Jelinek
2013-02-13 22:06     ` Jeff Law
2013-02-13 21:13 ` Steven Bosscher
2013-02-13 21:33   ` David Edelsohn
2013-02-13 23:18     ` John David Anglin
2013-02-13 23:42       ` Steven Bosscher
2013-02-13 23:49         ` Jakub Jelinek
2013-02-14 10:20           ` Steven Bosscher
2013-02-14 10:52             ` Jakub Jelinek
2013-02-14 12:49               ` Jeff Law
2013-02-15 15:08                 ` [PATCH] Disable PCH for -g other than dwarf[234] (PR pch/54117, take 2) Jakub Jelinek
2013-02-18 14:48                   ` John David Anglin
2013-02-18 17:58                   ` Jeff Law
2013-02-14 12:24       ` [PATCH] Temporarily revert Steven's PCH changes for 4.8 (PR pch/54117) Jeff Law
2013-02-14 21:15       ` Tom Tromey
2013-02-14 11:27     ` Steven Bosscher [this message]
2013-02-14 13:22       ` Tristan Gingold
2013-02-14 13:28         ` David Edelsohn
2013-02-15  0:10           ` Joel Brobecker
2013-02-18 23:07             ` Joel Brobecker
2013-02-19 15:51             ` David Edelsohn
2013-02-19 16:11               ` Joel Brobecker
2013-02-19 18:34                 ` David Edelsohn
2013-02-14 14:48         ` Steven Bosscher
2013-02-14 15:30           ` Tristan Gingold
2013-02-13 21:41   ` Douglas B Rupp
2013-02-19 20:57   ` Paolo Bonzini

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=CABu31nO_wThtZnKY6bnr47b9DyqABEvXbggit-o-amHaErv7Qw@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=danglin@gcc.gnu.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=law@redhat.com \
    --cc=rupp@gnat.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).