public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102029] New: ice:  error: type mismatch in ‘lshift_expr’
Date: Mon, 23 Aug 2021 19:47:56 +0000	[thread overview]
Message-ID: <bug-102029-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102029

            Bug ID: 102029
           Summary: ice:  error: type mismatch in ‘lshift_expr’
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For this C code:

$ more bug743.c
const long fmpz_neg_f2;
void qfb_reduce(void) { __gmpz_neg((int *)(fmpz_neg_f2 << 2)); }
$ 

Recent gcc trunk does this:

$ /home/dcb/gcc/results.20210823/bin/gcc  -c -O2 bug743.c 
bug743.c: In function ‘qfb_reduce’:
bug743.c:2:25: warning: implicit declaration of function ‘__gmpz_neg’
[-Wimplici
t-function-declaration]
    2 | void qfb_reduce(void) { __gmpz_neg((int *)(fmpz_neg_f2 << 2)); }
      |                         ^~~~~~~~~~
bug743.c:2:6: error: type mismatch in ‘lshift_expr’
    2 | void qfb_reduce(void) { __gmpz_neg((int *)(fmpz_neg_f2 << 2)); }
      |      ^~~~~~~~~~
int *
int *
int
_3 = fmpz_neg_f2.1_2 << 2;
bug743.c:2:6: internal compiler error: ‘verify_gimple’ failed
0xd9532a verify_gimple_in_seq(gimple*)
        ../../trunk.git/gcc/tree-cfg.c:5183

The problem first seems to appear sometime between git hash 
e92d0ff6b5e6d4b9 and 38757aa88735ab2e, about 40 commits.

             reply	other threads:[~2021-08-23 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 19:47 dcb314 at hotmail dot com [this message]
2021-08-23 19:50 ` [Bug middle-end/102029] [12 Regression] " pinskia at gcc dot gnu.org
2021-08-23 19:51 ` pinskia at gcc dot gnu.org
2021-08-23 20:21 ` jakub at gcc dot gnu.org
2021-08-23 21:52 ` roger at nextmovesoftware dot com
2021-08-24  2:00 ` cvs-commit at gcc dot gnu.org
2021-08-24  7:14 ` rguenth at gcc dot gnu.org
2021-08-24 12:23 ` dje at gcc dot gnu.org
2021-08-26 17:52 ` cvs-commit at gcc dot gnu.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-102029-4@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).