public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23476] New: [4.1 Regression] ICE in VRP, remove_range_assertions Date: Fri, 19 Aug 2005 06:19:00 -0000 [thread overview] Message-ID: <20050819061804.23476.pinskia@gcc.gnu.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1171 bytes --] Testcase: int h(int); static inline int f(int t, const int i) { _Bool a = i < t; if (a) return h(t); return 9; } int g(int t) { return f(t, 0x7FFFFFFF); } Compile with -O2 -fno-tree-copy-prop, and you will get an ICE: t.c: In function g: t.c:12: internal compiler error: in remove_range_assertions, at tree-vrp.c:2767 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. This most likely can be produced with a much larger source but I cannot find it right now as copy-prop does nothing interesting except for calling fold on all the statements which is just a waste of time. -- Summary: [4.1 Regression] ICE in VRP, remove_range_assertions Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23476
next reply other threads:[~2005-08-19 6:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-19 6:19 pinskia at gcc dot gnu dot org [this message] 2005-08-19 6:24 ` [Bug tree-optimization/23476] " pinskia at gcc dot gnu dot org 2005-08-19 9:05 ` pinskia at gcc dot gnu dot org 2005-08-19 13:17 ` dnovillo at gcc dot gnu dot org 2005-08-19 13:36 ` dnovillo at gcc dot gnu dot org 2005-08-19 18:10 ` cvs-commit at gcc dot gnu dot org 2005-08-19 18:17 ` dnovillo at gcc dot gnu dot org 2005-08-20 16:09 ` roger at eyesopen dot com
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=20050819061804.23476.pinskia@gcc.gnu.org \ --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).