public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33693]  New: [4.3 Regression] Type checking error with bitwise xor/and
Date: Mon, 08 Oct 2007 12:12:00 -0000	[thread overview]
Message-ID: <bug-33693-10053@http.gcc.gnu.org/bugzilla/> (raw)

unsigned long modify_field (unsigned long mask, long fieldval)
{
  return (~fieldval & ~mask);
}

value.2.min.i: In function 'modify_field':
value.2.min.i:2: error: type mismatch in binary expression
long unsigned int

long int

long unsigned int

D.1544 = fieldval | mask
value.2.min.i:2: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


-- 
           Summary: [4.3 Regression] Type checking error with bitwise
                    xor/and
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, ice-checking
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rguenth at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33693


             reply	other threads:[~2007-10-08 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 12:12 rguenth at gcc dot gnu dot org [this message]
2007-10-08 12:12 ` [Bug middle-end/33693] " rguenth at gcc dot gnu dot org
2007-10-08 15:24 ` rguenth at gcc dot gnu dot org
2007-10-08 15:32 ` rguenth at gcc dot gnu dot org

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=bug-33693-10053@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).