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: Mon, 01 Jul 2002 17:06:00 -0000 [thread overview] Message-ID: <20020702000603.903.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: Mark Mitchell <mark@codesourcery.com> Cc: Simon Shapiro <shimon@nomis-storage.com>, mmitchel@gcc.gnu.org <mmitchel@gcc.gnu.org>, gcc-bugs@gcc.gnu.org <gcc-bugs@gcc.gnu.org>, gcc-prs@gcc.gnu.org <gcc-prs@gcc.gnu.org>, nobody@gcc.gnu.org <nobody@gcc.gnu.org>, shimon@simon-shapiro.com <shSubject: Re: c/7139: Shifting 1 through a 64bit int fails at 32bit line Date: Mon, 01 Jul 2002 19:59:37 +0100 ------------------- > > > --On Thursday, June 27, 2002 06:26:25 PM +0100 Simon Shapiro > <shimon@nomis-storage.com> wrote: > > > Thax for looking into this problem. > > > > However, I would like to suggest that you may have dismissed the > > problem a bit too quickly. > > No, I understood it. > > You need to take a look at the C standard. > > If ints have 32 bits, (1 << 32) has undefined behavior. Great! Thanx. Simon > > -- > Mark Mitchell mark@codesourcery.com > CodeSourcery, LLC http://www.codesourcery.com > Sincerely, Simon Shapiro, CEO Nomis Storage, Inc.
next reply other threads:[~2002-07-02 0:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-01 17:06 Simon Shapiro [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-27 15:56 Mark Mitchell 2002-06-27 15:36 Simon Shapiro 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=20020702000603.903.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: linkBe 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).