public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joachim Ullrich <joachim.ullrich@siemens.com>
To: gcc@gcc.gnu.org
Subject: enumerators in generic tree
Date: Fri, 31 Mar 2017 16:25:00 -0000	[thread overview]
Message-ID: <58DE82FB.6040900@siemens.com> (raw)

I got the hint, that gcc-help might not be the best mailing list for my 
issue, therefor I post it here again (sorry for double-posting):

I work on a gcc plugin which provides a dependency model of the compiled 
sources.
The information is derived by walking the generic tree and collecting 
declarations of and references to all symbols. This works astonishingly 
good except for enumerators.

Enumerators are replaced by its constant value in a very early pass. The 
output generated by -fdump-tree-original doesn't show enumerator symbols 
but the constant value.

My question: is there an option to postpone the replacement of 
enumerators. I.e. to represent the enumerator as a CONST_DECL node 
instead of an INTEGER_CST node in the AST?
If there is no option, are there any other suggestions to solve the 
problem up to "patch" the gcc code?

Currently I am using gcc 4.8.2.

Thanks
Joachim

                 reply	other threads:[~2017-03-31 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=58DE82FB.6040900@siemens.com \
    --to=joachim.ullrich@siemens.com \
    --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).