From: Ian Lance Taylor <iant@google.com>
To: Rony Paul <ronypaul77@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: about named address space
Date: Tue, 24 May 2011 20:25:00 -0000 [thread overview]
Message-ID: <mcrr57ojhzb.fsf@coign.corp.google.com> (raw)
In-Reply-To: <BANLkTikE2p1R-ac=e+Vy=cE+4ETsho9WoQ@mail.gmail.com> (Rony Paul's message of "Mon, 23 May 2011 15:10:32 +0200")
Rony Paul <ronypaul77@gmail.com> writes:
> I user declare a variable "x", then when compiler executes that and
> stores in memory, can you tell me what is the rtx code for storing
> that variable? and in which file in GCC it is done?
It's difficult to answer that question in a simple way. Assuming you
are using C, the C frontend will create a VAR_DECL for x. If you assign
a value to that variable, it will create a MODIFY_EXPR. The MODIFY_EXPR
will then be converted to a GIMPLE_ASSIGN statement in GIMPLE. This
will then eventually be converted to an RTL SET. So the rtx code is
SET. If this is a local variable which is stored in memory rather than
in a register, the stack space will be allocated by assign_stack_local.
Ian
next prev parent reply other threads:[~2011-05-24 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 16:44 Rony Paul
2011-05-20 19:40 ` Rony Paul
2011-05-21 7:15 ` Ian Lance Taylor
2011-05-24 11:56 ` Rony Paul
2011-05-24 20:25 ` Ian Lance Taylor [this message]
2011-05-28 8:47 ` Rony Paul
2011-05-28 23:32 ` Ian Lance Taylor
2011-06-06 10:44 ` Rony Paul
2011-06-06 19:33 ` Rony Paul
2011-06-06 19:51 ` Ian Lance Taylor
[not found] <BANLkTinKZYCvTij1-7-X8+-_Zo_e77Y=8Q@mail.gmail.com>
[not found] ` <mcr7ha63553.fsf@coign.corp.google.com>
2011-05-04 15:45 ` Rony Paul
2011-05-04 17:35 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2011-05-02 9:18 Rony Paul
2011-05-02 20:14 ` Ian Lance Taylor
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=mcrr57ojhzb.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ronypaul77@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).