#2213 closed defect (fixed)
Decreased performance for whetstone benchmark using GCC >=4.5
Reported by: | daniel.cederman | Owned by: | Daniel Hellstrom |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | tool/gcc | Version: | |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
Moving from GCC 4.4.2 to 4.9.2 increases the execution time of the whetstone benchmark on both SPARC and x86. The cause seems to be a single commit. I have submitted a bug report to the GCC bugzilla:
Change History (10)
comment:1 Changed on 01/22/15 at 15:15:04 by Joel Sherrill
comment:2 Changed on 01/23/15 at 09:43:41 by daniel.cederman
Richard Biener provided a patch that fixed it on trunk. It looks like it could be easy to backport, but I have not had time to test it yet.
comment:3 Changed on 03/02/15 at 20:48:06 by Gedare Bloom
Milestone: | 4.11 → 4.11.1 |
---|
comment:4 Changed on 01/23/17 at 13:47:53 by Sebastian Huber
Owner: | set to Needs Funding |
---|---|
Status: | new → assigned |
How is the performance on GCC 6 or 7?
comment:5 Changed on 01/23/17 at 13:48:08 by Sebastian Huber
Owner: | changed from Needs Funding to Daniel Hellstrom |
---|
comment:6 Changed on 01/23/17 at 14:53:23 by daniel.cederman
A quick test shows that the performance for GCC 7 is about the same as for GCC 4.4.6.
GCC 4.4.6 => ~52 seconds
GCC 4.9.4 => ~55 seconds
GCC 7.0.0 (master at 20170116) => ~52 seconds
Compiled with -O3 and -mcpu=leon3.
comment:7 Changed on 01/23/17 at 14:55:31 by Sebastian Huber
Milestone: | 4.11.1 → 4.12 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Fixed in RTEMS 4.12, no plans to fix this in RTEMS 4.11.
comment:8 Changed on 05/11/17 at 07:31:02 by Sebastian Huber
Milestone: | 4.12 → 4.12.0 |
---|
comment:9 Changed on 10/10/17 at 05:58:26 by Sebastian Huber
Component: | GCC → tool/gcc |
---|
comment:10 Changed on 11/09/17 at 06:27:14 by Sebastian Huber
Milestone: | 4.12.0 → 5.1 |
---|
Milestone renamed
Note: See
TracTickets for help on using
tickets.
Daniel.. did this get resolved? I recall discussions.