This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Question on scalar replacement
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sun, 13 Jun 2004 20:10:08 -0400
- Subject: Re: Question on scalar replacement
- Organization: Red Hat Canada
- References: <10406132302.AA00184@vlsi1.ultra.nyu.edu>
On Sun, 2004-06-13 at 19:02, Richard Kenner wrote:
> # T.47_89 = PHI <T.47_31(4), T.47_35(23)>;
> # TMT.193_8 = PHI <TMT.193_93(4), TMT.193_86(23)>;
> # TMT.192_1 = PHI <TMT.192_91(4), TMT.192_87(23)>;
> # FRAME.64_85 = PHI <FRAME.64_32(4), FRAME.64_33(23)>;
> # j_6 = PHI <j_106(4), j_107(23)>;
> <L10>:;
> # TMT.192_94 = V_MAY_DEF <TMT.192_1>;
> # TMT.193_95 = V_MAY_DEF <TMT.193_8>;
> # FRAME.64_33 = V_MAY_DEF <FRAME.64_85>;
> FRAME.64.M12b = system__secondary_stack__ss_mark ();
>
So much for that idea. Set a breakpoint in tree-sra.c:scalarize_stmt
and continue until you hit this statement. Start stepping from there to
see why we don't rewrite the LHS of that assignment.
> There's simply *no* documentation at the start of the file at all containing
> any overview. It's not a matter of documentation being "easy" or "hard"
> to understand: it's not there at all!
>
OK. Look in tree-sra.c:tree_sra(). If you want, you could just move
that to the beginning of the file. It should be easy to fix the other
passes, if that's what you prefer.
Each tree-ssa pass is (should be) documented at its main entry point.
Entry points are all declared in the main pass sequencer
(tree-optimize.c:init_tree_optimization_passes).
Thanks. Diego.