public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc.hall at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33349] Redundant zero-extension of registers
Date: Thu, 16 Jun 2011 11:28:00 -0000 [thread overview]
Message-ID: <bug-33349-4-6odi7pPs7w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-33349-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33349
Jeremy <gcc.hall at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gcc.hall at gmail dot com
--- Comment #2 from Jeremy <gcc.hall at gmail dot com> 2011-06-16 11:27:24 UTC ---
Another example I came across ...
unsigned short sw;
asm( "fnstsw %0" : "=a" (sw) );
if( sw & FE_DIVBYZERO )
...
if( sw & FE_OVERFLOW )
...
if( sw & FE_UNDERFLOW )
...
generates:
movzx eax, ax # D.14460, sw
test al, 1 # D.14460,
test al, 4 # D.14460,
test al, 8 # D.14460,
next parent reply other threads:[~2011-06-16 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-33349-4@http.gcc.gnu.org/bugzilla/>
2011-06-16 11:28 ` gcc.hall at gmail dot com [this message]
2007-09-08 3:07 [Bug c++/33349] New: " us15 at os dot inf dot tu-dresden dot de
2009-02-06 21:45 ` [Bug middle-end/33349] " steven at gcc dot gnu dot org
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=bug-33349-4-6odi7pPs7w@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).