From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: tromey@redhat.com, Jan Kratochvil <jan.kratochvil@redhat.com>,
GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support DW_TAG_entry_point
Date: Fri, 24 Apr 2009 00:13:00 -0000 [thread overview]
Message-ID: <20090424001305.GL7552@adacore.com> (raw)
In-Reply-To: <6dc9ffc80904231649r37d4d106h7aece220a945a2d0@mail.gmail.com>
> > Assuming this is an extension, I would like a comment to that effect,
> > mentioning the compiler. Â A test case wouldn't hurt, either.
> >
>
> I do have a testcase. But you need ifort to use it.
We have a gdb.dwarf2 section where you can provide hard-coded dwarf2
data. That would be very helpful in making sure that we don't break
GDB with ifort's output later on.
--
Joel
prev parent reply other threads:[~2009-04-24 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 22:15 H.J. Lu
2009-03-21 1:02 ` Tom Tromey
2009-03-21 16:25 ` H.J. Lu
2009-03-23 18:26 ` Tom Tromey
2009-03-23 19:09 ` H.J. Lu
2009-04-22 21:13 ` Tom Tromey
2009-04-23 10:58 ` Joel Brobecker
2009-04-23 11:10 ` Jan Kratochvil
2009-04-23 23:43 ` Tom Tromey
2009-04-23 23:49 ` H.J. Lu
2009-04-24 0:13 ` Joel Brobecker [this message]
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=20090424001305.GL7552@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jan.kratochvil@redhat.com \
--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