public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rainy6144 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/44481] New: __builtin_parity() causes ICE in trunc_int_for_mode() Date: Wed, 09 Jun 2010 14:01:00 -0000 [thread overview] Message-ID: <bug-44481-9404@http.gcc.gnu.org/bugzilla/> (raw) When compiling the following program with -O2, gcc gives an ICE "internal compiler error: in trunc_int_for_mode, at explow.c:56". Versions affected: gcc (GCC) 4.4.3 20100127 (Red Hat 4.4.3-4) gcc (GCC) 4.5.1 20100521 (prerelease) ================================================ static inline unsigned parity(unsigned x) { return (unsigned) __builtin_parity(x); } unsigned f(unsigned rpoly) { return parity(rpoly & 1) ^ parity(rpoly & 6); } ================================================ -- Summary: __builtin_parity() causes ICE in trunc_int_for_mode() Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rainy6144 at gmail dot com GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44481
next reply other threads:[~2010-06-09 14:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-09 14:01 rainy6144 at gmail dot com [this message] 2010-06-11 18:25 ` [Bug rtl-optimization/44481] [4.3/4.4/4.5/4.6 Regression] " hjl dot tools at gmail dot com 2010-06-11 19:55 ` [Bug target/44481] " ubizjak at gmail dot com 2010-06-11 19:56 ` ubizjak at gmail dot com 2010-06-11 21:58 ` uros at gcc dot gnu dot org 2010-06-12 6:30 ` uros at gcc dot gnu dot org 2010-06-12 7:44 ` uros at gcc dot gnu dot org 2010-06-13 8:52 ` uros at gcc dot gnu dot org 2010-06-13 8:54 ` ubizjak at gmail 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=bug-44481-9404@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).