[PATCH] Hexagon Register Cleanup

Krzysztof Parzyszek kparzysz at codeaurora.org
Tue May 14 10:09:47 PDT 2013


On 5/14/2013 11:55 AM, Andrew Trick wrote:
>
> I completely understand. The point is, this isn’t something we want on
> trunk if it can be avoided. I won’t complain about any workaround you
> want to add in Target/Hexagon, and if you really need a hook into
> ScheduleInstrs that can be arranged. However, we run into this situation
> a lot, and the first tactic should be for the target to postprocess the
> DAG so we aren’t embedding target-specific workarounds in the generic
> DAG builder.

I see. That's fair enough.  I'll look into handling the DAG completely 
within our target code.  It may not happen tomorrow, though.  I will 
resubmit once I have a working solution.

Thank you for all comments.

-Krzysztof


-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, 
hosted by The Linux Foundation



More information about the llvm-commits mailing list