public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/94686] New: internal compiler error: in gimplify_expr Date: Tue, 21 Apr 2020 10:05:04 +0000 [thread overview] Message-ID: <bug-94686-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94686 Bug ID: 94686 Summary: internal compiler error: in gimplify_expr Product: gcc Version: 6.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com Target Milestone: --- Hi, the test.c (reduced by C-Reduce) #include <stdio.h> int a = 0,b = 0; int main(){ int c = (int)(long)(b * 0 >= a & b * 0 >= a); return 0; } $gcc-6 test.c then got the ICE error test.c: In function ‘main’: test.c:6:33: internal compiler error: in gimplify_expr, at gimplify.c:11192 int c = (int)(long)(b * 0 >= a & b * 0 >= a); ~~~~~~~~~~~~^~~~~~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions. My GCC version is $gcc-6 --version gcc-6 (Ubuntu 6.5.0-2ubuntu1~18.04) 6.5.0 20181026 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2020-04-21 10:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 10:05 haoxintu at gmail dot com [this message] 2020-04-21 10:33 ` [Bug c/94686] " jakub at gcc dot gnu.org 2020-04-21 10:49 ` 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-94686-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: 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).