This is the mail archive of the gcc-patches@gcc.gnu.org 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: [lto] PATCH: fill in code to merge declarations


Kenneth Zadeck wrote:

I do not think that this would work without a lot of work. I believe,
and the gimple elite can correct me, that there are non trivial
transformations in the control flow when the cfg is built and I cannot
just pack it back into a simple linear form.

You may be correct; I'm not sufficiently expert to know either. It might be that to make the plan I suggested work you would need to either run an out-of-SSA pass before writing out the trees, or that you would have to write the trees out earlier: after they become GENERIC, but before they become GIMPLE. But, it might well also be that even these measures would not work. Even if they do work, it might not be a good use of time to do that now, since the plan that you're advocating is the one that we really want.


I was going to just see what crashes after sandra fixes a couple of
dwarf bugs. I was thinking that maybe I could teach the cfg building
code to just leave the cfg alone if one is already there.

That makes sense to me. Of course, you'll have to audit for any other global variables or data structures that need to be set up -- hopefully there are not too many...


--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


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