public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/17106] New: Opportunity to eliminate loads from TOC. Date: Thu, 19 Aug 2004 14:59:00 -0000 [thread overview] Message-ID: <20040819145911.17106.steinmtz@us.ibm.com> (raw) Description: A non-optimal code sequence is illustraded. Duplicate using gcc 3.5 and command line: gcc -O3 -m64 -c test.c Testcase: static int s1, s2, s3; void no_common_toc1 () { s1 = 1; s2 = 2; s3 = 3; } Assembly: The code generated by gcc 3.5 contains loads the address from the TOC for each target location: .no_common_toc1: ld 11,.LC0@toc(2) li 0,1 li 9,2 ld 8,.LC2@toc(2) ld 10,.LC1@toc(2) stw 0,0(11) li 0,3 stw 9,0(10) stw 0,0(8) blr A single load of the base of the TOC is all that is needed: .no_common_toc1: ld 11,.LC0@toc(2) li 0,1 li 9,2 stw 0,0(11) li 0,3 stw 9,4(11) stw 0,8(11) blr -- Summary: Opportunity to eliminate loads from TOC. Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: enhancement Priority: P1 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: steinmtz at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org,steinmtz at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17106
next reply other threads:[~2004-08-19 14:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-19 14:59 gcc-bugzilla at gcc dot gnu dot org [this message] 2004-08-19 15:21 ` [Bug tree-optimization/17106] " pinskia at gcc dot gnu dot org 2004-11-06 20:37 ` pinskia at gcc dot gnu dot org 2005-09-10 18:02 ` pinskia 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=20040819145911.17106.steinmtz@us.ibm.com \ --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).