public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46556] Code size regression in struct access Date: Wed, 01 Aug 2012 13:04:00 -0000 [thread overview] Message-ID: <bug-46556-4-gPkCWEFUIJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46556-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46556 --- Comment #9 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-08-01 13:02:46 UTC --- Author: wschmidt Date: Wed Aug 1 13:02:38 2012 New Revision: 190037 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190037 Log: gcc: PR tree-optimization/46556 * gimple-ssa-strength-reduction.c (enum cand_kind): Add CAND_REF. (base_cand_map): Change to hash table. (base_cand_hash): New function. (base_cand_free): Likewise. (base_cand_eq): Likewise. (lookup_cand): Change base_cand_map to hash table. (find_basis_for_candidate): Likewise. (base_cand_from_table): Exclude CAND_REF. (restructure_reference): New function. (slsr_process_ref): Likewise. (find_candidates_in_block): Call slsr_process_ref. (dump_candidate): Handle CAND_REF. (base_cand_dump_callback): New function. (dump_cand_chains): Change base_cand_map to hash table. (replace_ref): New function. (replace_refs): Likewise. (analyze_candidates_and_replace): Call replace_refs. (execute_strength_reduction): Change base_cand_map to hash table. gcc/testsuite: PR tree-optimization/46556 * testsuite/gcc.dg/tree-ssa/slsr-27.c: New. * testsuite/gcc.dg/tree-ssa/slsr-28.c: New. * testsuite/gcc.dg/tree-ssa/slsr-29.c: New. Added: trunk/gcc/testsuite/gcc.dg/tree-ssa/slsr-27.c trunk/gcc/testsuite/gcc.dg/tree-ssa/slsr-28.c trunk/gcc/testsuite/gcc.dg/tree-ssa/slsr-29.c Modified: trunk/gcc/ChangeLog trunk/gcc/gimple-ssa-strength-reduction.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-08-01 13:04 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-19 9:04 [Bug rtl-optimization/46556] New: " amodra at gmail dot com 2010-11-21 23:12 ` [Bug rtl-optimization/46556] " amodra at gmail dot com 2010-11-22 10:24 ` rguenth at gcc dot gnu.org 2010-11-22 10:43 ` amodra at gmail dot com 2010-11-22 10:50 ` amodra at gmail dot com 2010-11-22 11:20 ` rguenther at suse dot de 2010-11-22 11:49 ` steven at gcc dot gnu.org 2011-01-19 8:50 ` amodra at gmail dot com 2011-02-07 11:42 ` steven at gcc dot gnu.org 2012-06-28 16:12 ` [Bug tree-optimization/46556] " wschmidt at gcc dot gnu.org 2012-08-01 13:04 ` wschmidt at gcc dot gnu.org [this message] 2012-08-01 13:05 ` wschmidt at gcc dot gnu.org 2012-08-01 13:06 ` wschmidt at gcc dot gnu.org 2012-08-01 17:53 ` steven at gcc dot gnu.org 2012-08-01 18:43 ` wschmidt 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-46556-4-gPkCWEFUIJ@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).