public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/67421] gcc.dg/wide-shift-64.c FAILs Date: Thu, 03 Sep 2015 09:16:00 -0000 [thread overview] Message-ID: <bug-67421-4-pv6IbReRxa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67421-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67421 --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #1 from Jiong Wang <jiwang at gcc dot gnu.org> --- > (In reply to Rainer Orth from comment #0) >> Created attachment 36275 [details] >> wide-shift-64.c.219r.combine >> >> The new gcc.dg/wide-shift-64.c testcase FAILs on SPARC for the 64-bit >> multilib >> only: >> >> FAIL: gcc.dg/wide-shift-64.c scan-rtl-dump-not combine "ior" >> >> I'm attaching the dump. > > Rainer, > > I am trying to reproduce this on my cross environment while I can't. > > And searching in your dump file, I haven't found "ior" so the testcase should > have passed. I just noticed I must have been dreaming when submitting this bug report: it's the *32-bit* case that fails, not the 64-bit one. I'm attaching the correct dump this time. > Can you please have a quick looks at the compile options used when testing > this testcase in your multi-lib environment, then I can reproduce in my local > sparc x86 cross env where I only have cc1 configured with --target=sparc-linux. cc1 is invoked like this for a 32-bit-default configuration: $ cc1 -quiet wide-shift-64.c -mcpu=v9 -O2 -fdump-rtl-combine -o wide-shift-64.s Rainer
next prev parent reply other threads:[~2015-09-03 9:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-01 12:43 [Bug middle-end/67421] New: " ro at gcc dot gnu.org 2015-09-01 12:44 ` [Bug middle-end/67421] " ro at gcc dot gnu.org 2015-09-02 10:27 ` jiwang at gcc dot gnu.org 2015-09-03 9:16 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2015-09-03 9:17 ` ro at gcc dot gnu.org 2015-09-03 10:31 ` jiwang at gcc dot gnu.org 2015-09-10 10:37 ` jiwang at gcc dot gnu.org 2015-09-10 10:44 ` jiwang 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-67421-4-pv6IbReRxa@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).