Displaying 3 results from an estimated 3 matches for "updatedbgloc".
2017 Nov 06
3
[RFC] Setting the current debug loc when the insertion point changes
...ug without changing IRBuilder's behavior.
# Solutions
1. Add a method called SetInsertPointAndDebugLoc() which behaves identically to the current SetInsertPoint(). Change SetInsertPoint() so that it doesn't change the current debug loc.
2. Add a boolean argument to SetInsertPoint() called UpdateDbgLoc which defaults to false. Only change the current debug loc if UpdateDbgLoc is true.
I have a mild preference for idea #1 because it's easier to read, IMO.
Whichever solution we pick, my plan is to first migrate all in-tree users of SetInsertPoint() to the explicit API, and to then gradually f...
2017 Nov 06
2
[RFC] Setting the current debug loc when the insertion point changes
...>>
>> # Solutions
>>
>> 1. Add a method called SetInsertPointAndDebugLoc() which behaves identically to the current SetInsertPoint(). Change SetInsertPoint() so that it doesn't change the current debug loc.
>> 2. Add a boolean argument to SetInsertPoint() called UpdateDbgLoc which defaults to false. Only change the current debug loc if UpdateDbgLoc is true.
>>
>> I have a mild preference for idea #1 because it's easier to read, IMO.
>>
>> Whichever solution we pick, my plan is to first migrate all in-tree users of SetInsertPoint() to the e...
2017 Nov 06
2
[RFC] Setting the current debug loc when the insertion point changes
...lutions
>>>>
>>>> 1. Add a method called SetInsertPointAndDebugLoc() which behaves identically to the current SetInsertPoint(). Change SetInsertPoint() so that it doesn't change the current debug loc.
>>>> 2. Add a boolean argument to SetInsertPoint() called UpdateDbgLoc which defaults to false. Only change the current debug loc if UpdateDbgLoc is true.
>>>>
>>>> I have a mild preference for idea #1 because it's easier to read, IMO.
>>>>
>>>> Whichever solution we pick, my plan is to first migrate all in-tree us...