This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/55073] Wrong Neon code generation at -O2 caused by -fschedule-insns
- From: "eric.batut at allegorithmic dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 30 Nov 2012 16:16:36 +0000
- Subject: [Bug target/55073] Wrong Neon code generation at -O2 caused by -fschedule-insns
- Auto-submitted: auto-generated
- References: <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