public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61757] [4.10 Regression] genmodes failure with enable-checking Date: Fri, 11 Jul 2014 23:03:00 -0000 [thread overview] Message-ID: <bug-61757-4-y7mJe1Od7o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61757-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61757 --- Comment #19 from Pat Haugen <pthaugen at gcc dot gnu.org> --- Tracked down the problem in 176.gcc to a difference in the generated code for benchmark source toplev.c:exact_log2_wide(). Following compiled with -O3 -mcpu=power7. int exact_log2_wide (unsigned int x) { register int log = 0; if (x == 0 || x != (x & -x)) return -1; while ((x >>= 1) != 0) log++; return log; } r212351: neg 9,3 and 9,9,3 cmplw 7,9,3 bne 7,.L5 >>> rldicl. 9,9,63,33 li 3,0 beq 0,.L6 r212352: neg 10,3 and 10,10,3 cmplw 7,10,3 bne 7,.L5 >>> srdi. 9,3,1 li 3,0 beq 0,.L6 r212351 is clearing the high word of the 64-bit register on the initial shift right of 'x', whereas r212352 just starts shifting the whole 64-bit reg. The reason this causes problems is that the callers are calling with an integer arg: #define exact_log2(N) exact_log2_wide ((HOST_WIDE_INT) (N)) So in the case where MIN_INT32 is passed (sign extended), the upper 32 bits are '1' so r212352 returns a value of 63 whereas prior revisions returned a value of 31. Not sure if this is more of a benchmark source error, but figured I'd post my findings in case it helps with the general problem. >From gcc-bugs-return-456150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 12 01:42:52 2014 Return-Path: <gcc-bugs-return-456150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18840 invoked by alias); 12 Jul 2014 01:42:52 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 18782 invoked by uid 48); 12 Jul 2014 01:42:48 -0000 From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57644] [C++1y] Cannot bind bitfield to lvalue reference Date: Sat, 12 Jul 2014 01:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: emsr at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: <bug-57644-4-s7lpa2b7gY@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-57644-4@http.gcc.gnu.org/bugzilla/> References: <bug-57644-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-07/txt/msg00741.txt.bz2 Content-length: 472 https://gcc.gnu.org/bugzilla/show_bug.cgi?idW644 emsr at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |emsr at gcc dot gnu.org Resolution|--- |FIXED --- Comment #5 from emsr at gcc dot gnu.org --- Fixed on trunk...
next prev parent reply other threads:[~2014-07-11 23:03 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-09 7:51 [Bug bootstrap/61757] New: " dcb314 at hotmail dot com 2014-07-09 8:56 ` [Bug bootstrap/61757] " dominiq at lps dot ens.fr 2014-07-09 10:14 ` ktkachov at gcc dot gnu.org 2014-07-09 11:56 ` [Bug bootstrap/61757] [4.10 Regression] " rguenth at gcc dot gnu.org 2014-07-09 12:45 ` [Bug tree-optimization/61757] " schwab@linux-m68k.org 2014-07-09 13:09 ` schwab@linux-m68k.org 2014-07-09 20:47 ` dominiq at lps dot ens.fr 2014-07-10 9:36 ` rguenth at gcc dot gnu.org 2014-07-10 9:39 ` ktkachov at gcc dot gnu.org 2014-07-10 10:29 ` schwab@linux-m68k.org 2014-07-10 14:43 ` rguenth at gcc dot gnu.org 2014-07-10 14:49 ` rguenth at gcc dot gnu.org 2014-07-11 13:29 ` rguenth at gcc dot gnu.org 2014-07-11 13:45 ` dominiq at lps dot ens.fr 2014-07-11 14:07 ` ro at gcc dot gnu.org 2014-07-11 14:26 ` schwab@linux-m68k.org 2014-07-11 16:16 ` pthaugen at gcc dot gnu.org 2014-07-11 17:24 ` matz at gcc dot gnu.org 2014-07-11 17:47 ` matz at gcc dot gnu.org 2014-07-11 18:32 ` schwab@linux-m68k.org 2014-07-11 23:03 ` pthaugen at gcc dot gnu.org [this message] 2014-07-13 13:39 ` dominiq at lps dot ens.fr 2014-07-13 17:32 ` segher at gcc dot gnu.org 2014-07-14 1:23 ` danglin at gcc dot gnu.org 2014-07-14 8:56 ` rguenth at gcc dot gnu.org 2014-07-14 9:04 ` rguenth at gcc dot gnu.org 2014-07-14 9:17 ` rguenth at gcc dot gnu.org 2014-07-14 9:48 ` rguenth at gcc dot gnu.org 2014-07-14 10:51 ` rguenth at gcc dot gnu.org 2014-07-14 10:51 ` rguenth at gcc dot gnu.org 2014-07-14 17:57 ` pthaugen at gcc dot gnu.org 2014-07-14 19:15 ` law at redhat dot com 2014-07-15 7:45 ` rguenther at suse dot de 2015-01-16 5:37 ` law at redhat 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-61757-4-y7mJe1Od7o@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).