From: Doug Evans <dje@google.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Tristan Gingold <gingold@adacore.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: AIX DWARF debugging sections
Date: Tue, 06 Oct 2015 20:00:00 -0000 [thread overview]
Message-ID: <CADPb22Q1s4q7NCzUO5iLt0cT8ewH21RhmHTnyPh7AS=4nhFmsw@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnykS9J5cHfbDg4swVhXZdJ+Lzk7JQmikbPrXh2E4p-xshg@mail.gmail.com>
On Tue, Oct 6, 2015 at 11:24 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
> On Tue, Oct 6, 2015 at 12:51 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>> > Because the AIX section does not use the standard name, I am unsure
>>> > which it represents. The documentation only states "dwmac", which
>>> > could expand to either name.
>>> >
>>> > Thanks, David
>>>
>>> Yeah, I think we need to figure out which one it is.
>>
>> That's what I have been trying to do, but I don't see any evidence
>> that GCC emits it, or that binutils handles it. So the answer must
>> lie somewhere on the system side. David?
>
> The official answer from IBM XLC is the section is for both
> .debug_macinfo and .debug_macro
>
> For DWARF4 and below, the dwmac section corresponds to .debug_macinfo.
> For DWARF5 and above, the dwmac section corresponds to .debug_macro.
>
> XLC currently does not generate any macro debugging information for DWARF4.
Huh.
Let's make sure this is documented in the code.
next prev parent reply other threads:[~2015-10-06 20:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 14:53 David Edelsohn
2015-09-28 13:41 ` Tristan Gingold
2015-10-02 21:32 ` Joel Brobecker
2015-10-02 22:35 ` David Edelsohn
2015-10-06 0:30 ` Doug Evans
2015-10-06 16:52 ` Joel Brobecker
2015-10-06 16:55 ` David Edelsohn
2015-10-06 18:24 ` David Edelsohn
2015-10-06 20:00 ` Doug Evans [this message]
2015-10-07 12:49 ` David Edelsohn
2015-10-10 0:04 ` Joel Brobecker
[not found] ` <CADPb22QmuPeP_QBDNWA4iSi1jsnTvAiAurV8HWGCAYnPoMr+wg@mail.gmail.com>
2015-10-10 2:58 ` David Edelsohn
2015-10-12 15:50 ` Joel Brobecker
2015-10-12 17:41 ` David Edelsohn
2015-10-12 18:34 ` Joel Brobecker
2015-10-13 15:33 ` David Edelsohn
2015-10-13 16:45 ` Joel Brobecker
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='CADPb22Q1s4q7NCzUO5iLt0cT8ewH21RhmHTnyPh7AS=4nhFmsw@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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