Alias analysis or DSE problem?

I'm currently porting a plug-in that used to target the 4.3.0-based plug-in branch to the new top-of-tree plug-in system. I'm really stymied by a bug whose source I just cannot track down! Usually that means there is an error in my code, but the problem seems to involve tree-ssa-dse.c and tree-ss

Re: Alias analysis or DSE problem?

Thanks a lot for the help! It looks like creating a temporary took care of it. On Sat, Oct 17, 2009 at 7:41 AM, Richard Guenther wrote: > I think the call you insert is not of valid gimple form - an address > argument has to fulfill the is_gimple_min_invariant() predicate. > Thus I suspect you h

Re: Alias analysis or DSE problem?

oking at this. --Justin On Tue, Oct 20, 2009 at 5:18 AM, Richard Guenther wrote: > On Tue, Oct 20, 2009 at 1:34 AM, Justin Seyster wrote: >> Thanks a lot for the help!  It looks like creating a temporary >> took care of it. >> >> On Sat, Oct 17, 2009 at 7:41 AM, R

Re: tree check: expected SSA_NAME, have var_decl

You can assign the "a" TREE_NODE to a temporary variable and call make_ssa_name on the temp, allowing you to use it as an argument to a GIMPLE_CALL. Here is the function I use for that purpose: /* Create a GIMPLE statement assigning a reference to a temporary variable, add that statement at th

[plugins] Name for pass_all_optimizations

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

Re: Plugins & GGC ie GTY

Sorry for dragging this discussion out from the distant past. I'm in the process of porting some plug-ins from the old plugin SVN branch to the new plug-in system, and this is one of the issues blocking me. My plug-ins maintain some tree nodes that I want to stay alive from function to function.

Re: [plugins] Name for pass_all_optimizations

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 &

Plug-in Licensing

I'm getting ready to release plug-in code, and I want to have a very clear idea about licensing before I release. I'm leaning towards releasing everything as GPLv3, but I do want to know exactly what is and isn't allowed. I know this issue was debated quite intensely before plug-in support got ad

Re: Plug-in Licensing

have when releasing a stand-alone GCC plug-in. It sounds like the GPLv3 will do that for me, so that's my plan unless somebody corrects me. --Justin On Tue, Oct 19, 2010 at 4:49 PM, Ian Lance Taylor wrote: > Justin Seyster writes: > >> I'm getting ready to release

A Framework for GCC Plug-ins

One of my research projects for the past few months has been a framework for writing GCC instrumentation plug-ins called InterAspect. I am releasing the project today, and since there is a general interest in plug-ins on this list, I wanted to send a quick announcement with a pointer to the web sit