public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>,
	       Jason Merrill <jason@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch 10/10] debug-early merge: compiler proper
Date: Mon, 01 Jun 2015 15:43:00 -0000	[thread overview]
Message-ID: <556C7D81.30504@redhat.com> (raw)
In-Reply-To: <CAFiYyc3FKVgko0-ozdHropratHfmbAoDYqT_1TqmOCDvVDN2_g@mail.gmail.com>

On 06/01/2015 04:04 AM, Richard Biener wrote:
> On Mon, Jun 1, 2015 at 10:03 AM, Richard Biener
> <richard.guenther@gmail.com> wrote:
>> On Sun, May 31, 2015 at 10:38 PM, Jason Merrill <jason@redhat.com> wrote:
>>> On 05/30/2015 08:52 PM, Aldy Hernandez wrote:
>>>>
>>>> On 05/29/2015 03:33 PM, Jason Merrill wrote:
>>>>>
>>>>> On 05/29/2015 03:26 PM, Richard Biener wrote:
>>>>>>
>>>>>> ISTR I had to mark the gimple reg used for the bound as
>>>>>> non-DECL_IGNORED for the LTO stuff.
>>>>>
>>>>>
>>>>> Let's go with that, then.
>>>>
>>>>
>>>> Well, I did play around with that option originally, but temporaries do
>>>> not end up in the symbol table, so we won't see them to feed them to
>>>> late_global_decl.
>>>
>>>
>>> The temporary has function scope, so I don't see why that would be an issue.
>>
>> Yeah, we should walk it via the function_decl hook on the containing function.
>
> Btw, the following was my gimplify.c hunk:
>
> diff --git a/gcc/gimplify.c b/gcc/gimplify.c
> index d822913..10a9318 100644
> --- a/gcc/gimplify.c
> +++ b/gcc/gimplify.c
> @@ -8994,6 +8994,12 @@ gimplify_one_sizepos (tree *expr_p, gimple_seq *stmt_p)
>     *expr_p = unshare_expr (expr);
>
>     gimplify_expr (expr_p, stmt_p, NULL, is_gimple_val, fb_rvalue);
> +
> +  /* The possibly generated temporary is interesting for debug information
> +     to complete the VLA type sizes and bounds.  Clear DECL_IGNORED_P.  */
> +  if (TREE_CODE (*expr_p) == VAR_DECL
> +      && DECL_ARTIFICIAL (*expr_p))
> +    DECL_IGNORED_P (*expr_p) = false;

We still have the problem that function locals in dwarf2out are seen in 
decls_for_scope by iterating through BLOCK_VARS, and temporaries do not 
live in BLOCK_VARS.

How did they get picked up and annotated in your approach?

Aldy

  reply	other threads:[~2015-06-01 15:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  0:41 Aldy Hernandez
2015-05-18 11:06 ` Richard Biener
2015-05-18 14:47   ` Jan Hubicka
     [not found]   ` <555CAD35.5040304@redhat.com>
2015-05-20 21:03     ` Aldy Hernandez
2015-05-20 21:11       ` Jan Hubicka
2015-05-20 22:11         ` Aldy Hernandez
2015-05-22  9:00           ` Eric Botcazou
2015-05-22 11:45           ` Richard Biener
2015-05-22 13:41             ` Aldy Hernandez
2015-05-22 11:26     ` Richard Biener
2015-05-22 14:29       ` Aldy Hernandez
2015-05-27 13:18         ` Richard Biener
2015-05-27 12:50     ` Jason Merrill
2015-05-28 20:12       ` Aldy Hernandez
2015-05-28 20:54         ` Jason Merrill
2015-05-28 21:01           ` Jan Hubicka
2015-05-28 21:10             ` Jason Merrill
2015-05-28 21:16               ` Jan Hubicka
2015-05-29 12:07           ` Richard Biener
2015-05-29 19:33           ` Aldy Hernandez
2015-05-29 19:40             ` Richard Biener
2015-05-29 19:49               ` Jason Merrill
2015-05-31  7:53                 ` Aldy Hernandez
2015-05-31 22:14                   ` Jason Merrill
2015-06-01  8:03                     ` Richard Biener
2015-06-01  8:04                       ` Richard Biener
2015-06-01 15:43                         ` Aldy Hernandez [this message]
2015-06-01 17:01                           ` Richard Biener
2015-06-01 17:42                             ` Aldy Hernandez
2015-06-02  8:13                               ` Richard Biener
2015-06-02 19:25                                 ` Aldy Hernandez
2015-05-29 19:47             ` Jason Merrill
2015-05-28 21:31       ` Aldy Hernandez
2015-05-29  6:33         ` Jason Merrill

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=556C7D81.30504@redhat.com \
    --to=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jason@redhat.com \
    --cc=richard.guenther@gmail.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).