Great! I actually got around to submitting a patch before the
weekend, but Andrew Pinski noted that naming these passes results in
some unwanted dump files. I plan to have a patch ready soon to fix
that up.
--Justin
On Tue, May 12, 2009 at 8:02 AM, Diego Novillo wrote:
> On Thu, Apr 23,
On Thu, Apr 23, 2009 at 22:58, Justin Seyster wrote:
> Unless that's not a good place to put plug-in passes, I propose
> giving the pass_all_optimizations pass the name "all_optimizations."
> I believe that there are a handful of other unnamed passes that might
> also be useful for plug-in dev
I'm working on porting a plug-in designed for the old
branches/plugin branch to the (recently merged) shiny new
branches/plugins branch. One thing that's turning out to be tricky is
placing the plug-in transform in exactly the same place. In the old
branch, plug-ins hook in just before the pa
