From: Martin Jambor <mjambor@suse.cz>
To: Erick Ochoa <eochoa@gcc.gnu.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Question on path from C parser to DECL_INITIAL
Date: Wed, 23 Mar 2022 13:46:50 +0100 [thread overview]
Message-ID: <ri6o81wx2dh.fsf@suse.cz> (raw)
In-Reply-To: <CAJ_nqziLv-GwDWR+ME+py4_Ac-t=Sqb=LKGdXTx3m=Z3_azJpg@mail.gmail.com>
Hi,
On Wed, Mar 23 2022, Erick Ochoa via Gcc wrote:
> Hi,
>
> I am trying to understand what path is executed in GCC from parsing a C
> expression (in a global variable declaration) to the value in DECL_INITIAL.
> At the moment, I have annotated a tree during parsing. I have another
> debugging pass that looks for this tree in subsequent passes. The
> annotation persists if the tree is inside a function body. However, if the
> tree is in a global variable initialization (i.e., DECL_INITIAL), then I am
> unable to see the annotation even when placing the debugging pass at the
> beginning of passes.def.
>
> Can someone provide a little bit of guidance?
Sounds like a gdb watchpoint should help here.
Martin
prev parent reply other threads:[~2022-03-23 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 11:53 Erick Ochoa
2022-03-23 12:23 ` Richard Biener
2022-03-23 12:31 ` Erick Ochoa
2022-03-23 12:46 ` Martin Jambor [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=ri6o81wx2dh.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=eochoa@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).