This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/53659] ARM: Using -mcpu=cortex-a9 option results in bad performance for Cortex-A9 processor in C-Ray phoronix benchmark
- From: "tulipawn at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 14 Feb 2017 17:54:33 +0000
- Subject: [Bug target/53659] ARM: Using -mcpu=cortex-a9 option results in bad performance for Cortex-A9 processor in C-Ray phoronix benchmark
- Auto-submitted: auto-generated
- References: <bug-53659-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659
--- Comment #12 from PeteVine <tulipawn at gmail dot com> ---
Nice, PR68664 patch has fixed the issue.
FWIW, unlike previously, running on a Cortex-A53, showed perfect alignment with
core type (-mfpu=vfpv3) on the first run:
Cortex-A8
Rendering took: 1 seconds (1801 milliseconds)
Cortex-A5
Rendering took: 1 seconds (1708 milliseconds)
Cortex-A7
Rendering took: 1 seconds (1699 milliseconds)
Cortex-A9
Rendering took: 1 seconds (1644 milliseconds)
Cortex-A15
Rendering took: 1 seconds (1637 milliseconds)
whereas using -mfpu=vfpv4 favours Cortex-A5 code's execution:
Cortex-A8
Rendering took: 1 seconds (1803 milliseconds)
Cortex-A5
Rendering took: 1 seconds (1506 milliseconds)
Cortex-A7
Rendering took: 1 seconds (1636 milliseconds)
Cortex-A9
Rendering took: 1 seconds (1645 milliseconds)
Cortex-A15
Rendering took: 1 seconds (1643 milliseconds)
but that's probably expected. Not sure about A8's codegen performance though.