public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pinskia@physics.uc.edu To: gcc-gnats@gcc.gnu.org Subject: c++/10717: Performance issue in expand_static_init with large number of static initializors Date: Fri, 09 May 2003 19:36:00 -0000 [thread overview] Message-ID: <20030509192717.14452.qmail@sources.redhat.com> (raw) >Number: 10717 >Category: c++ >Synopsis: Performance issue in expand_static_init with large number of static initializors >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri May 09 19:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Andrew Pinski >Release: 3.4 >Organization: >Environment: powerpc-darwin (all really, does not matter). >Description: This is related to http://gcc.gnu.org/PR?10060 as the code is the same but the problem is different. cp_finish_decl (cp/decl.c:8221) calls expand_static_init (cp/decl.c:8512) calls value_member and value_member looks though a linked list which is very ineffienct, a better way is to use a hashtable. >How-To-Repeat: See http://gcc.gnu.org/PR?10060 how to generate the file and compile it, it will ice when compiling (but that is the problem for that PR). >Fix: Use a hashtable instead of a linked list. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-09 19:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030509192717.14452.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-gnats@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).