From: Josh Huber <huberj@wpi.edu>
To: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: gcc bug
Date: Fri, 31 Mar 2000 09:27:07 -0500 [thread overview]
Message-ID: <20000331092707.C354@wpi.edu> (raw)
Interesting gcc bug here...
in both cases this should print 0xDEADBEEF, but in the second case, garbage
is printed.
main()
{
unsigned long t1 = 32;
unsigned long long t2 = 64;
printf("%x\n", 1 ? 0xDEADBEEF : t1);
printf("%x\n", 1 ? 0xDEADBEEF : t2);
}
as expected, the 1 ? ... operation is optimized away, but the compiler seems
to screw things up ...
working case:
li 4,15
crxor 6,6,6
bl printf
failure case:
li 5,0
li 6,15
crxor 6,6,6
bl printf
in the failure case, r4 is not loaded with anything, so this is were the
garbage probably comes from.
This is a greatly simplified version of an actual piece of code (obviously,
as the code above is silly :)
Josh
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-31 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 14:27 Josh Huber [this message]
2000-03-31 15:18 ` gcc bug Gabriel Paubert
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=20000331092707.C354@wpi.edu \
--to=huberj@wpi.edu \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).