From: David Edelsohn <dje@watson.ibm.com>
To: Thomas Graichen <graichen@innominate.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: shifts on 64bit ints
Date: Thu, 03 Aug 2000 19:02:31 -0400 [thread overview]
Message-ID: <200008032302.TAA29224@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Thomas Graichen <news-innominate.list.linux.ppc.dev@innominate.de> of "03 Aug 2000 22:38:06 GMT." <news2mail-8mcs8e$kdj$2@mate.bln.innominate.de>
First, I would suggest that you use a printf format like "%08x"
for better legibility.
Second, I tried your example with gcc-2.95.2 on PowerPC AIX
gcc-2.95.2 on PowrePC Linux, and a recent development snapshot of GCC with
various optimization levels (you did not specify what options you used to
compile the testcase) and I consistently saw the following output:
Mask 29 is 0x0000000020000000 - 0xffffffffdfffffff
Mask 30 is 0x0000000040000000 - 0xffffffffbfffffff
Mask 31 is 0x0000000080000000 - 0xffffffff7fffffff
Mask 32 is 0x0000000100000000 - 0xfffffffeffffffff
Mask 33 is 0x0000000200000000 - 0xfffffffdffffffff
Mask 34 is 0x0000000400000000 - 0xfffffffbffffffff
You appear to have a problem, but it is local to your system
(could be toolchain or C library as well).
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-03 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <news-innominate.list.linux.ppc.dev@innominate.de>
2000-08-03 22:38 ` shifts on 64bit ints Thomas Graichen
2000-08-03 23:02 ` David Edelsohn [this message]
2000-08-03 23:54 ` Franz Sirl
2000-08-04 0:40 ` Takashi Oe
2000-08-04 0:50 ` Takashi Oe
2000-08-04 7:16 ` Thomas Graichen
2000-08-04 9:21 ` Gabriel Paubert
2000-08-04 15:18 ` David Edelsohn
2000-08-04 15:28 ` Kevin B. Hendricks
2000-08-04 16:06 ` Getting things in... Was: " Tom Gall
2000-08-04 16:26 ` David Edelsohn
2000-08-04 16:30 ` Tom Gall
2000-08-04 17:49 ` Benjamin Herrenschmidt
2000-08-04 18:32 ` Takashi Oe
2000-08-04 18:52 ` Hendricks, Kevin
2000-08-04 19:44 ` Takashi Oe
2000-08-04 20:10 ` Michael Schmitz
2000-08-05 5:42 ` Paul Mackerras
2000-08-05 11:51 ` Geert Uytterhoeven
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=200008032302.TAA29224@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=graichen@innominate.de \
--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).