From: nkavv@physics.auth.gr
To: gcc-help@gcc.gnu.org
Subject: Attempting changes to the GIMPLifier
Date: Thu, 19 Apr 2012 10:40:00 -0000 [thread overview]
Message-ID: <20120419134327.13086nomkt65d2os@mail.physics.auth.gr> (raw)
Dear all,
I have a few questions regarding how to augment the information dumped
in "004t" GIMPLE dumps (prior any optimization).
My main concerns are:
1. Printing global variables.
2. Preserving function arguments (what I call an "interface").
Both 1 and 2 are not currently addressed, at least in the gcc-4.5.1
and gcc-4.6.0 gimplifiers that I work with.
Is this information available in internal data structures so I can
expose it via use of the GIMPLE API?
I've also noticed inconsistencies among GIMPLE dumps produced
following different optimizations, but this is another topic.
Thanks in advance.
Best regards,
Nikolaos Kavvadias
reply other threads:[~2012-04-19 10:40 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=20120419134327.13086nomkt65d2os@mail.physics.auth.gr \
--to=nkavv@physics.auth.gr \
--cc=gcc-help@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).