public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51109] New: bdver1 scheduler state machine too large Date: Sat, 12 Nov 2011 21:19:00 -0000 [thread overview] Message-ID: <bug-51109-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2011-11-12 20:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-12 21:19 andi-gcc at firstfloor dot org [this message] 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
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-51109-4@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: linkBe 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).