public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: Erwin.Unruh@fujitsu-siemens.com, Heinrich.Brand@fujitsu-siemens.com, Joachim.Canisius@fujitsu-siemens.com, Servatius.Brandt@fujitsu-siemens.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, neil@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/6346: sign extension missing after cast down and up on long long bitfield Date: Wed, 22 May 2002 05:09:00 -0000 [thread overview] Message-ID: <20020522120900.23012.qmail@sources.redhat.com> (raw) Synopsis: sign extension missing after cast down and up on long long bitfield Responsible-Changed-From-To: unassigned->neil Responsible-Changed-By: neil Responsible-Changed-When: Wed May 22 05:08:57 2002 Responsible-Changed-Why: Bitfield issues are assigned to me, though I doubt I'll have time to fix them until 3.3. State-Changed-From-To: open->analyzed State-Changed-By: neil State-Changed-When: Wed May 22 05:08:57 2002 State-Changed-Why: Bitfields have several issues, fundamentally down to the single fact that their type is not represented properly in the compiler. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6346
next reply other threads:[~2002-05-22 12:09 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-22 5:09 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-18 1:56 Servatius.Brandt
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=20020522120900.23012.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=Erwin.Unruh@fujitsu-siemens.com \ --cc=Heinrich.Brand@fujitsu-siemens.com \ --cc=Joachim.Canisius@fujitsu-siemens.com \ --cc=Servatius.Brandt@fujitsu-siemens.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).