search for: laziest

...the callee function to change the lowering of a call. Since AMDGPUDAGToDAGISel is ultimately a normal MachineFunction pass, I'm able to get the interprocedural analysis pass there but don't have a way to pass this into the call lowering where it's actually needed. >> >> The laziest option would be to stash the pointer to the analysis in the TargetMachine and get it from there, but is probably not the best idea. Another option might be to store a pointer to the SelectionDAGISel pass in SelectionDAG, so then there's a way to access the pass to get analysis directly. Is ther...

...use knowledge of the callee function to change the lowering of a call. Since AMDGPUDAGToDAGISel is ultimately a normal MachineFunction pass, I'm able to get the interprocedural analysis pass there but don't have a way to pass this into the call lowering where it's actually needed. The laziest option would be to stash the pointer to the analysis in the TargetMachine and get it from there, but is probably not the best idea. Another option might be to store a pointer to the SelectionDAGISel pass in SelectionDAG, so then there's a way to access the pass to get analysis directly. Is ther...

I've been adding some new flow statements to my compiler and realize the easiest/laziest way to produce the DAG is just to store a flow variable and end blocks with a "switch" branch. It appears the optimizers do a fine job of unwinding the nonsense, reducing the conditions, and even expanding the trailing paths. For example, I terminate my blocks with a logical switch like...

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

Hi edA-qa mort-ora-y, On 17/04/13 21:27, edA-qa mort-ora-y wrote: > I've been adding some new flow statements to my compiler and realize the > easiest/laziest way to produce the DAG is just to store a flow variable > and end blocks with a "switch" branch. It appears the optimizers do a > fine job of unwinding the nonsense, reducing the conditions, and even > expanding the trailing paths. > > For example, I terminate my blocks wit...

...ToDAGISel is ultimately a >>>> normal MachineFunction pass, I'm able to get the interprocedural >>>> analysis pass there but don't have a way to pass this into the call >>>> lowering where it's actually needed. >>>> >>>> The laziest option would be to stash the pointer to the analysis in >>>> the TargetMachine and get it from there, but is probably not the >>>> best idea. Another option might be to store a pointer to the >>>> SelectionDAGISel pass in SelectionDAG, so then there's a wa...