public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22501] [meta-bug] tramp3d-v4 missed optimizations
Date: Sat, 14 Jan 2006 14:30:00 -0000	[thread overview]
Message-ID: <20060114143040.25818.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22501-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rguenth at gcc dot gnu dot org  2006-01-14 14:30 -------
Subject: Bug 22501

Author: rguenth
Date: Sat Jan 14 14:30:33 2006
New Revision: 109703

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109703
Log:
2006-01-14  Richard Guenther  <rguenther@suse.de>

        PR tree-optimization/22548
        PR tree-optimization/22555
        PR tree-optimization/22501
        * Makefile.in (tree-ssa-structalias.o): Depend on $(PARAMS_H).
        * params.def (salias-max-array-elements): New parameter.
        * params.h (SALIAS_MAX_ARRAY_ELEMENTS): Define.
        * doc/invoke.texi (salias-max-array-elements): Document.
        * tree-flow-inline.h (var_can_have_subvars): We also handle
        arrays now.
        * tree-ssa-alias.c (find_used_portions): Handle ARRAY_REF like
        COMPONENT_REF.
        * tree-ssa-structalias.c (params.h): Include.
        (push_fields_onto_fieldstack): Handle ARRAY_TYPE.
        (find_func_aliases): Handle multiple constraints from ARRAY_REF.
        (get_constraint_for): For ADDR_EXPR operating on something
        containing an ARRAY_REF, add all subvars to the solution.
        (handle_ptr_arith): Handle ARRAY_TYPE like RECORD_TYPE types.
        * tree-ssa-operands.c (parse_ssa_operands): Handle ARRAY_REF
        for creating MUST_DEFs.
        (get_expr_operands): Treat ARRAY_REF like COMPONENT_REF wrt subvars.

        * gcc.dg/tree-ssa/alias-4.c: New testcase.
        * gcc.dg/tree-ssa/alias-5.c: Likewise.
        * gcc.dg/tree-ssa/alias-6.c: Likewise.
        * gcc.dg/tree-ssa/alias-7.c: Likewise.
        * gcc.dg/tree-ssa/alias-8.c: Likewise.
        * gcc.dg/tree-ssa/alias-9.c: Likewise.
        * gcc.dg/tree-ssa/alias-10.c: Likewise.
        * gcc.dg/tree-ssa/alias-11.c: Likewise.
        * gcc.dg/tree-ssa/alias-12.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-10.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-11.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-12.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-4.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-5.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-6.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-7.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-8.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-9.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/Makefile.in
    trunk/gcc/doc/invoke.texi
    trunk/gcc/params.def
    trunk/gcc/params.h
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-flow-inline.h
    trunk/gcc/tree-ssa-alias.c
    trunk/gcc/tree-ssa-operands.c
    trunk/gcc/tree-ssa-structalias.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22501


  parent reply	other threads:[~2006-01-14 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22501-10053@http.gcc.gnu.org/bugzilla/>
2005-11-30 20:55 ` rguenth at gcc dot gnu dot org
2006-01-14 14:30 ` rguenth at gcc dot gnu dot org [this message]
2006-02-25 20:15 ` pinskia at gcc dot gnu dot org
     [not found] <bug-22501-4@http.gcc.gnu.org/bugzilla/>
2015-03-26  3:15 ` hubicka at gcc dot gnu.org
2015-03-26 10:54 ` rguenth at gcc dot gnu.org
2005-07-15 13:23 [Bug tree-optimization/22501] New: " rguenth at gcc dot gnu dot org
2005-07-15 13:29 ` [Bug tree-optimization/22501] [meta-bug] " pinskia at gcc dot gnu dot org
2005-07-15 13:32 ` rguenth at gcc dot gnu dot org
2005-07-18 14:52 ` rguenth 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=20060114143040.25818.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: link
Be 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).