public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: gandalf@winds.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	neil@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c/5593: GCC miscompiles bitshifts on unsigned struct members when creating a 64-bit value
Date: Sun, 10 Feb 2002 19:02:00 -0000	[thread overview]
Message-ID: <20020211030233.3031.qmail@sources.redhat.com> (raw)

Synopsis: GCC miscompiles bitshifts on unsigned struct members when creating a 64-bit value

Responsible-Changed-From-To: unassigned->neil
Responsible-Changed-By: rth
Responsible-Changed-When: Sun Feb 10 19:02:32 2002
Responsible-Changed-Why:
    Pretty sure this is more fodder for your bitfield patch.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5593


             reply	other threads:[~2002-02-11  3:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10 19:02 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-09  4:16 neil
2002-11-08 20:46 Byron Stanoszek
2002-11-08  1:06 Christian Ehrhardt
2002-11-05  8:15 bangerth
2002-02-05 11:46 gandalf

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=20020211030233.3031.qmail@sources.redhat.com \
    --to=rth@gcc.gnu.org \
    --cc=gandalf@winds.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=neil@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).