search for: collectdebugvalues

Displaying 4 results from an estimated 4 matches for "collectdebugvalues".

2018 May 07
0
Ideas for managing DBG_VALUE machine instructions.
...by all different machine > passes, the immediate question is now what utility functions should be > made available for common use. [... snip ...] > We are discussing where to place these utility functions, and if > splice() should optionally be made to do this also. It seems that > collectDebugValues() in MachineSink.cpp is a good starting point, but we > probably want to do an even better search than just looking at the first > def operand. > > It would be nice to get some general feedback from the community at this > point so we know which direction to take... I'm unbiase...
2018 May 08
3
DEBUG INFO: improve handling of DBG_VALUEs and DebugLocs in CodeGen
...My personal understanding right now is that 2 is not vital but should be done on a best-effort basis. 1 however is really bad if it happens (which it currently does). We are discussing where to place these utility functions, and if splice() should optionally be made to do this also. It seems that collectDebugValues() in MachineSink.cpp is a good starting point, but we probably want to do an even better search than just looking at the first def operand. It would be nice to get some general feedback from the community at this point so we know which direction to take... /Jonas
2018 May 08
0
DEBUG INFO: improve handling of DBG_VALUEs and DebugLocs in CodeGen
...is case is to remove the debug information (e.g., by inserting line: 0 locations) instead of providing incorrect or partially correct information. > > We are discussing where to place these utility functions, and if > splice() should optionally be made to do this also. It seems that > collectDebugValues() in MachineSink.cpp is a good starting point, but we > probably want to do an even better search than just looking at the first > def operand. > > It would be nice to get some general feedback from the community at this > point so we know which direction to take... Thank you for s...
2018 May 04
0
gberry@codeaurora.org
...personal understanding right now is that 2 is not vital but should be done on a best-effort basis. 1 however is really bad if it happens (which it currently does). We are discussing where to place these utility functions, and if splice() should optionally be made to do this also. It seems that collectDebugValues() in MachineSink.cpp is a good starting point, but we probably want to do an even better search than just looking at the first def operand. It would be nice to get some general feedback from the community at this point so we know which direction to take... /Jonas