From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Mark Mitchell <mark@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: potiential problems with parm decls.
Date: Wed, 01 Aug 2007 14:16:00 -0000 [thread overview]
Message-ID: <46B095B0.8080202@naturalbridge.com> (raw)
Mark,
How are you (we) handling PARM_DECLS?
Honza has informed my that the PARM_DECLS in the function's
DECL_ARGUMENTS needs to be "==" to the set of PARM_DECLS accessed in the
function.
How are you setting DECL_ARGUMENTS for functions?
Am I supposed to be building this for the functions that I am
processing? If so, what about the functions that i am not processing?
Otherwise, i think that we are going to need something like lto_parm_ref
and lto_resolve_parm_ref.
Kenny
next reply other threads:[~2007-08-01 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 14:16 Kenneth Zadeck [this message]
2007-08-01 17:23 ` Mark Mitchell
2007-08-01 17:34 ` Kenneth Zadeck
2007-08-02 0:43 ` Mark Mitchell
2007-08-02 1:10 ` Kenneth Zadeck
2007-08-02 2:50 ` Mark Mitchell
2007-08-01 20:44 ` [lto] PATCH COMMITTED " Kenneth Zadeck
2007-08-01 22:12 ` Tom Tromey
2007-08-01 22:36 ` Kenneth Zadeck
2007-08-02 1:06 ` [lto] PATCH COMMITTED to fix missing semicolons Kenneth Zadeck
2007-08-02 1:16 ` David Daney
2007-08-02 1:49 ` Andrew Pinski
2007-08-02 16:42 ` Kenneth Zadeck
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=46B095B0.8080202@naturalbridge.com \
--to=zadeck@naturalbridge.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.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).