public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric.batut at allegorithmic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55073] Wrong Neon code generation at -O2 caused by -fschedule-insns
Date: Fri, 30 Nov 2012 16:18:00 -0000	[thread overview]
Message-ID: <bug-55073-4-VJGqrPoupo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55073-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55073

--- Comment #13 from Eric Batut <eric.batut at allegorithmic dot com> 2012-11-30 16:16:36 UTC ---
Richard,

After a clean checkout of gcc's trunk and of the Android NDK r8b package and
tools, I rebuilt arm-linux-androideabi-gcc on a Ubuntu VM using gcc 4.5.1. I
then rebuilt my testcase with "-O1" and "-O1 -fno-dse", and the same difference
is there: d19 and d21 are used as sources for the two vmovl.s8 instead of d18
and d20.

I attach a new tarball with the (very slightly) modified source I am using, the
two assembly files that are generated, and the two binary files (they should
run on any Android device, no fancy stuff here). Could you please use your
local build of gcc to generate the same assembly files so that we can compare
the function bodies?

Best Regards,
Eric


  parent reply	other threads:[~2012-11-30 16:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 12:54 [Bug target/55073] New: " eric.batut at allegorithmic dot com
2012-10-25 23:02 ` [Bug target/55073] " steven at gcc dot gnu.org
2012-11-29 17:52 ` rearnsha at gcc dot gnu.org
2012-11-29 18:05 ` rearnsha at gcc dot gnu.org
2012-11-30  9:52 ` eric.batut at allegorithmic dot com
2012-11-30  9:58 ` rearnsha at gcc dot gnu.org
2012-11-30 10:14 ` eric.batut at allegorithmic dot com
2012-11-30 11:05 ` eric.batut at allegorithmic dot com
2012-11-30 13:21 ` eric.batut at allegorithmic dot com
2012-11-30 14:00 ` rearnsha at gcc dot gnu.org
2012-11-30 14:29 ` eric.batut at allegorithmic dot com
2012-11-30 14:40 ` rearnsha at gcc dot gnu.org
2012-11-30 14:56 ` rearnsha at gcc dot gnu.org
2012-11-30 15:17 ` eric.batut at allegorithmic dot com
2012-11-30 16:18 ` eric.batut at allegorithmic dot com [this message]
2012-11-30 16:21 ` eric.batut at allegorithmic dot com
2012-11-30 17:29 ` rearnsha at gcc dot gnu.org
2012-11-30 18:50 ` rearnsha 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-55073-4-VJGqrPoupo@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: link
Be 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).