From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: jit@gcc.gnu.org
Subject: lvalues and rvalues
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <CACXZuxemh6PZS1deAj39FmGRsjkTYrLtDRJqDZnvBK2REo-gZA@mail.gmail.com> (raw)
I am still trying to get the lvalue / rvalue concepts so that I know
exactly what to use when.
I have struct with a pointer member.
struct X {
struct Y *base;
};
Now this pointer base can be updated while the function is running so
I need the value of the pointer refreshed (loaded) whenever it can
potentially change. In LLVM I emit explicit load instructions which
are then optimized so that any redundant loads are deleted. What would
be the equivalent method here? Should I just use a rvalue reference?
Will this be automatically refreshed? Should I use a local variable
and assign the value of the base pointer to it explicitly (i.e.
similar to explicit load) ?
Thanks and Regards
Dibyendu
next reply other threads:[~2015-06-14 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Dibyendu Majumdar [this message]
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
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=CACXZuxemh6PZS1deAj39FmGRsjkTYrLtDRJqDZnvBK2REo-gZA@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=jit@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).