public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/51109] New: bdver1 scheduler state machine too large
@ 2011-11-12 21:19 andi-gcc at firstfloor dot org
2012-10-10 9:37 ` [Bug target/51109] " ubizjak at gmail dot com
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: andi-gcc at firstfloor dot org @ 2011-11-12 21:19 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
Bug #: 51109
Summary: bdver1 scheduler state machine too large
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: andi-gcc@firstfloor.org
CC: harsha.jagasia@amd.com, hubicka@gcc.gnu.org
I noticed that the i386 bdver1 scheduler generates some of the largest symbols
in the compiler, much larger than any of the other x86 scheduler state machines
% nm -t d --size-sort .../cc1 | c++filt | tail
...
0000000000040480 r bdver1_int_min_issue_delay
...
0000000000161920 r bdver1_int_transitions
Likely that means it's slow too.
Honza thought it was a bug, so I'm filling it for reference.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/51109] bdver1 scheduler state machine too large
2011-11-12 21:19 [Bug target/51109] New: bdver1 scheduler state machine too large andi-gcc at firstfloor dot org
@ 2012-10-10 9:37 ` ubizjak at gmail dot com
2012-10-10 9:38 ` ubizjak at gmail dot com
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: ubizjak at gmail dot com @ 2012-10-10 9:37 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2012-10-10 09:37:21 UTC ---
Author: vekumar
Date: Wed Oct 10 09:19:11 2012
New Revision: 192296
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192296
Log:
Fix for PR51109
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/bdver1.md
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/51109] bdver1 scheduler state machine too large
2011-11-12 21:19 [Bug target/51109] New: bdver1 scheduler state machine too large andi-gcc at firstfloor dot org
2012-10-10 9:37 ` [Bug target/51109] " ubizjak at gmail dot com
@ 2012-10-10 9:38 ` ubizjak at gmail dot com
2012-10-10 9:39 ` Ganesh.Gopalasubramanian at amd dot com
2012-10-10 10:56 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: ubizjak at gmail dot com @ 2012-10-10 9:38 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86
Status|UNCONFIRMED |RESOLVED
URL| |http://gcc.gnu.org/ml/gcc-p
| |atches/2012-09/msg01822.htm
| |l
Resolution| |FIXED
Target Milestone|--- |4.8.0
--- Comment #2 from Uros Bizjak <ubizjak at gmail dot com> 2012-10-10 09:38:17 UTC ---
Fixed.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/51109] bdver1 scheduler state machine too large
2011-11-12 21:19 [Bug target/51109] New: bdver1 scheduler state machine too large andi-gcc at firstfloor dot org
2012-10-10 9:37 ` [Bug target/51109] " ubizjak at gmail dot com
2012-10-10 9:38 ` ubizjak at gmail dot com
@ 2012-10-10 9:39 ` Ganesh.Gopalasubramanian at amd dot com
2012-10-10 10:56 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: Ganesh.Gopalasubramanian at amd dot com @ 2012-10-10 9:39 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
--- Comment #3 from GGanesh <Ganesh.Gopalasubramanian at amd dot com> 2012-10-10 09:39:08 UTC ---
Thanks a lot Uros, Venkat!
-----Original Message-----
From: ubizjak at gmail dot com [mailto:gcc-bugzilla@gcc.gnu.org]
Sent: Wednesday, October 10, 2012 3:07 PM
To: Gopalasubramanian, Ganesh
Subject: [Bug target/51109] bdver1 scheduler state machine too large
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2012-10-10 09:37:21
UTC ---
Author: vekumar
Date: Wed Oct 10 09:19:11 2012
New Revision: 192296
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192296
Log:
Fix for PR51109
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/bdver1.md
--
Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You are on the CC list for
the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/51109] bdver1 scheduler state machine too large
2011-11-12 21:19 [Bug target/51109] New: bdver1 scheduler state machine too large andi-gcc at firstfloor dot org
` (2 preceding siblings ...)
2012-10-10 9:39 ` Ganesh.Gopalasubramanian at amd dot com
@ 2012-10-10 10:56 ` jakub at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: jakub at gcc dot gnu.org @ 2012-10-10 10:56 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51109
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-10 10:55:59 UTC ---
Author: jakub
Date: Wed Oct 10 10:55:54 2012
New Revision: 192305
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192305
Log:
PR target/51109
* config/i386/bdver1.md (bdver1-mult): Remove.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/bdver1.md
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-10-10 10:56 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-12 21:19 [Bug target/51109] New: bdver1 scheduler state machine too large andi-gcc at firstfloor dot org
2012-10-10 9:37 ` [Bug target/51109] " ubizjak at gmail dot com
2012-10-10 9:38 ` ubizjak at gmail dot com
2012-10-10 9:39 ` Ganesh.Gopalasubramanian at amd dot com
2012-10-10 10:56 ` jakub at gcc dot gnu.org
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).