This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: birthpoints in rtl.

>  The two complications are:
> 1) libcalls

I am probably dense here, but why we can't just ignore existence of
libcalls for dataflow framework?  This exist so we can effectivly remove
blocks of code in dead code removal and do some other changes, but I
don't see how they can be less friendly to FUD than they are to DU/UD.
Sure the optimization has to care to not break the extra invariant that
libcalls stay independent, but that is.

Overall yes, I certainly would hope they can go. Just I don't see direct
dependency with this project.
> 2) how do you merge different types of subregs stores. 
> We have our best people working on (1) and the hope is that unless
> someone adds a killer reason to enhancement bugzilla 35413, we should be
> able to make that abomination go away forever.  I plan to clear
> enhancement bugzilla 35404 this weekend.
> I am still hoping for one of the subreg elite to volunteer to help me
> with (2). 

Subregs don't seem to be too different here. The reads of subregs are
equivalent with any other use.  The stores are bit funnier since some
cases (subregs of multiword pseudos or STRICT_LOW_PART) behave as read
write operations.  Only problem here seems to be that wihtout lowering
the multiword operation we have some extra uses of undefined variables
but this conservative handling should be good enough for most cases.
For introducing the PHI operations you do not need to worry if the value
originated in SUBREG or not.

> Then my plan is to "adapt" as much of the tree ssa code (there is no
> reason for me to write dominance frontier code for the 4 time from
> scratch) as possible to inserting the noop moves where the phi would
> normally go and adapt the renaming step to build the chains. I have not
> read the fud papers closely, but reif's trick of using for using the
> birthpoints means that you can actually avoid having to solve reaching
> defs, and can just adapt the ssa stack based renaming algorithm to build
> the chains rather than rename the vars.  I have no idea if wolfe ever
> figured this part out or not. 
> Kenny

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]