* gcc and x86 condition codes
@ 2009-07-01 21:56 Amitabha Roy
0 siblings, 0 replies; 2+ messages in thread
From: Amitabha Roy @ 2009-07-01 21:56 UTC (permalink / raw)
To: gcc
Hi
I am working on transforming x86 binaries generated with gcc and
wanted to know whether gcc treats the eflags register as a single unit
when generating code or actually tracks individual flags.
My question is motivated by an optimisation I am making in my tool
that assumes that any instruction that writes to the eflags register
kills it and no subsequent instructions can try to access any flags
not written by this instruction. Is this assumption correct in current
gcc (>= 4.0.0). A search led me to this message
http://gcc.gnu.org/ml/gcc/2005-11/msg00206.html
which says that it is true, or at least was true back then.
Cheers
-Amitabha
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-07-01 22:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <a975b8520907011449x34f9991ay6b5502cbc6f39bd1@mail.gmail.com>
2009-07-01 22:19 ` gcc and x86 condition codes Richard Henderson
2009-07-01 21:56 Amitabha Roy
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).