public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/41399] [4.5 Regression] Scheduler gives huge dependence graph compiling fortran/intrinsic.c on ARM Date: Fri, 29 Jan 2010 10:19:00 -0000 [thread overview] Message-ID: <20100129101848.29156.qmail@sourceware.org> (raw) In-Reply-To: <bug-41399-276@http.gcc.gnu.org/bugzilla/> ------- Comment #20 from rearnsha at gcc dot gnu dot org 2010-01-29 10:18 ------- (In reply to comment #18) > Function that seems to cost the most time is add_functions(), which is one big > basic block of ~7500 insns (~500 of them call insns). > > List scheduling is quadratic in the number of insns per basic block. I don't > know the scheduler very well, but I would expect GCC has some kind of moving > window to limit the number of insns we consider for scheduling within a basic > block. If so, then this is broken now. > Sched-deps.c contains the following chunk of code: if (!deps->readonly && ((deps->pending_read_list_length + deps->pending_write_list_length) > MAX_PENDING_LIST_LENGTH)) { /* Flush all pending reads and writes to prevent the pending lists from getting any larger. Insn scheduling runs too slowly when these lists get long. When compiling GCC with itself, this flush occurs 8 times for sparc, and 10 times for m88k using the default value of 32. */ flush_pending_lists (deps, insn, false, true); } but presumably this is not being triggered any more. > That doesn't explain why only ARM seems to be hit by this, though. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41399
next prev parent reply other threads:[~2010-01-29 10:19 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-18 14:02 [Bug bootstrap/41399] New: [4.5 Regression] Internal error compiling fortran/intrinsic.c danglin at gcc dot gnu dot org 2009-09-18 21:00 ` [Bug bootstrap/41399] " ramana at gcc dot gnu dot org 2009-09-18 21:52 ` dave at hiauly1 dot hia dot nrc dot ca 2009-09-20 20:58 ` pinskia at gcc dot gnu dot org 2009-09-21 8:47 ` ramana at gcc dot gnu dot org 2009-09-22 14:12 ` dave at hiauly1 dot hia dot nrc dot ca 2009-10-07 15:09 ` dave at hiauly1 dot hia dot nrc dot ca 2009-10-09 17:22 ` danglin at gcc dot gnu dot org 2009-10-23 20:39 ` danglin at gcc dot gnu dot org 2009-10-24 11:54 ` rguenth at gcc dot gnu dot org 2009-11-02 14:15 ` dave at hiauly1 dot hia dot nrc dot ca 2009-11-17 0:20 ` danglin at gcc dot gnu dot org 2009-11-27 11:10 ` rguenth at gcc dot gnu dot org 2009-12-02 16:07 ` dave at hiauly1 dot hia dot nrc dot ca 2009-12-07 16:02 ` dave at hiauly1 dot hia dot nrc dot ca 2009-12-07 17:01 ` ramana at gcc dot gnu dot org 2009-12-08 11:47 ` ramana at gcc dot gnu dot org 2009-12-08 11:54 ` [Bug target/41399] " rguenth at gcc dot gnu dot org 2009-12-11 9:54 ` ramana at gcc dot gnu dot org 2010-01-28 21:55 ` steven at gcc dot gnu dot org 2010-01-28 23:04 ` steven at gcc dot gnu dot org 2010-01-28 23:23 ` steven at gcc dot gnu dot org 2010-01-28 23:48 ` [Bug target/41399] [4.5 Regression] Scheduler gives huge dependence graph compiling fortran/intrinsic.c on ARM steven at gcc dot gnu dot org 2010-01-29 10:19 ` rearnsha at gcc dot gnu dot org [this message] 2010-01-29 21:54 ` vmakarov at redhat dot com 2010-01-29 22:47 ` steven at gcc dot gnu dot org 2010-02-01 19:53 ` vmakarov at gcc dot gnu dot org 2010-02-01 22:14 ` steven at gcc dot gnu dot 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=20100129101848.29156.qmail@sourceware.org \ --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).