public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Simon Shapiro <shimon@nomis-storage.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7139: Shifting 1 through a 64bit int fails at 32bit line
Date: Thu, 27 Jun 2002 15:36:00 -0000	[thread overview]
Message-ID: <20020627222601.2699.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/7139; it has been noted by GNATS.

From: Simon Shapiro <shimon@nomis-storage.com>
To: mmitchel@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, shimon@simon-shapiro.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/7139: Shifting 1 through a 64bit int fails at 32bit line
Date: Thu, 27 Jun 2002 18:26:25 +0100

 Thax for looking into this problem.
 
 However, I would like to suggest that you may have dismissed the
 problem a bit too quickly.
 
 I am making this bold assumption based on my understanding that:
 
 1 << 31 = 0x0000000080000000, and not 0xffffffff80000000
 1 << 32 = 0x0000000100000000, and not  0x0000000000000001
 
 Am I wrong?
 
 Perhaps the example was 
 too complicated.  Try this one:
 #include <stdio.h>
 
 int 
 main()
 {
         unsigned long long      i64;
         int                                     index;
 
 
         for (index = 0; index < 64; index++) {
                 i64 = 1 << index;
 
                 (void)fprintf(stdout, "1 << %d = %qx\n", index, i64);
         }
  
         return(0);
 }
 
 -------------------
 > Synopsis: Shifting 1 through a 64bit int fails at 32bit line
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: mmitchel
 > State-Changed-When: Thu Jun 27 15:07:03 2002
 > State-Changed-Why:
 >     Not a defect.
 > 
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g
 cc&pr=7139
 > 
 Sincerely,
 
 Simon Shapiro, CEO
 Nomis Storage, Inc.


             reply	other threads:[~2002-06-27 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 15:36 Simon Shapiro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-01 17:06 Simon Shapiro
2002-06-27 15:56 Mark Mitchell
2002-06-27 15:12 mmitchel

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=20020627222601.2699.qmail@sources.redhat.com \
    --to=shimon@nomis-storage.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).