From: Pierre-Marie de Rodat <derodat@adacore.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 6 Status Report (2015-10-16)
Date: Tue, 20 Oct 2015 15:47:00 -0000 [thread overview]
Message-ID: <562660C9.4010900@adacore.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1510161108250.29931@zhemvz.fhfr.qr>
Hi Richard,
On 10/16/2015 05:09 AM, Richard Biener wrote:
> This means it is time to get things you want to have in GCC 6 finalized
> and reviewed. As usual there may be exceptions to late reviewed features
> but don't count on that. Likewise target specific features can sneak in
> during Stage 3 if maintainers ok them.
This is just to point out I have series of DWARF-related patches
awaiting reviews for several months. I plan to rebase against trunk,
retest and resubmit them shortly but hereâs an overview:
* The patch series for transition to standard DWARF for Ada
(https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01857.html). There are 8
patches, each one depending on the previous one, except the 6/8 one
(https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01361.html) which could
go on its own.
* Fix DW_AT_static_link generation in DWARF
(https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01855.html). The
corresponding support in GDB is in the development branch.
* Track indirect calls as call site information in DWARF
(https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01856.html).
* Materialize subprogram renamings in Ada as imported declarations in
DWARF (https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01854.html). The
corresponding support in GDB is in the development branch.
If there is anything I should do to ease the review process, please let
me know. :-) Thank you in advance!
--
Pierre-Marie de Rodat
next prev parent reply other threads:[~2015-10-20 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 9:12 Richard Biener
2015-10-20 15:47 ` Pierre-Marie de Rodat [this message]
2015-10-20 16:02 ` Jeff Law
2015-10-20 19:38 ` Pierre-Marie de Rodat
2015-10-20 19:54 ` Jeff Law
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=562660C9.4010900@adacore.com \
--to=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).