Displaying 10 results from an estimated 10 matches for "gramanas".
2018 Apr 25
2
[GSoC 2018] Improve Debugging of Optimized Code
Hello,
My proposal for GSoC 2018 [attachment] about
improving debugging of optimized code was accepted.
I will work with my mentor Vedant Kumar (vsk) through the summer to
find where DI loss occurs and try to fix as many occurrences as possible.
I will also be keeping a devlog here: https://gramanas.github.io/
You can check what the first steps of my project are on the latest post:
https://gramanas.github.io/posts/community-bonding/
I'd love to hear any thoughts or questions you might have.
Cheers,
Anastasis
-------------- next part --------------
A non-text attachment was scrubbed...
N...
2018 Apr 25
0
[GSoC 2018] Improve Debugging of Optimized Code
...SoC 2018 [attachment] about
> improving debugging of optimized code was accepted.
>
> I will work with my mentor Vedant Kumar (vsk) through the summer to
> find where DI loss occurs and try to fix as many occurrences as possible.
>
> I will also be keeping a devlog here: https://gramanas.github.io/
>
> You can check what the first steps of my project are on the latest post:
> https://gramanas.github.io/posts/community-bonding/
>
> I'd love to hear any thoughts or questions you might have.
>
> Cheers,
> Anastasis
2018 Apr 25
1
[GSoC 2018] Improve Debugging of Optimized Code
...out
>> improving debugging of optimized code was accepted.
>>
>> I will work with my mentor Vedant Kumar (vsk) through the summer to
>> find where DI loss occurs and try to fix as many occurrences as possible.
>>
>> I will also be keeping a devlog here: https://gramanas.github.io/
>>
>> You can check what the first steps of my project are on the latest post:
>> https://gramanas.github.io/posts/community-bonding/
>>
>> I'd love to hear any thoughts or questions you might have.
>>
>> Cheers,
>> Anastasis
> __...
2018 Feb 26
1
[GSoC 2018] Improving debugging of optimized code
...me bugs (not necessarily related to the
aforementioned project) I would appreciate it.
I would also like some more information about the first goal of the
project, like an outline of the procedure you have in mind for gathering
debug loss metrics.
I'll be in llvm's IRC with the nick "gramanas" in case you want to PM me.
Best regards,
Anastasis
[1] https://mixxx.org/wiki/doku.php/crate_enhancements
[2] https://llvm.org/OpenProjects.html#llvm_optimized_debugging
2018 Apr 26
2
Debugify and Verify-each mode
...pply and check debugify of FunctionPasses since these passes are managed by Function Pass Managers created on the fly during schedulePass(). I guess we'd have to implement the FunctionPass version of Debugify and CheckDebugify.
Yes, Anastasis (CC'd) has started exploring this idea: https://gramanas.github.io/posts/community-bonding/ <https://gramanas.github.io/posts/community-bonding/>. Please sync up with him before you start hacking, so you can collaborate on the design and split up work :). Now that GSoC has officially started, Anastasis needs to plan work ahead of time, so we need t...
2018 May 30
0
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
...9; instructions. To confirm this
> I did:
>
> $ grep "ERROR: Instruction" results | grep phi -c
>
> witch gives us a result of `5214' and this means that all the
> instructions with missing Debug Loc are `phi' instructions.
>
>
> [Here] https://gramanas.github.io/sroa-results.csv
>
>
> Conclusion
> ==========
>
> This implies SROA does a pretty good job of preserving debug values.
>
That is good to hear / expected, since we went though great lengths to ensure that SROA preserves variable debug info.
Have you looked at...
2018 Apr 26
0
Debugify and Verify-each mode
Hi Vedant,
I have tried to implement the fix you proposed, but it didn't work as
expected. I created a new *Module* Pass Manager (not Function Pass Manager)
and override the *add()* method like this:
class DebugifyEachPassManager : public legacy::PassManager {
public:
void add(Pass *P) override {
PassManager::add(createDebugifyPass());
PassManager::add(P);
2018 Mar 16
2
Debugify and Verify-each mode
Mhm I see now, thanks for your explanation!
Son Tuan Vu
On Fri, Mar 16, 2018 at 10:58 PM, Vedant Kumar <vsk at apple.com> wrote:
>
> On Mar 16, 2018, at 2:30 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> Hi Vedant,
>
> Thank you for your reply. I think I can make this debugify-each mode, but
> I guess this is reserved for your GSoC project ?
>
>
2018 May 30
4
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
...instructions with missing DL were `phi' instructions. To confirm this
I did:
$ grep "ERROR: Instruction" results | grep phi -c
witch gives us a result of `5214' and this means that all the
instructions with missing Debug Loc are `phi' instructions.
[Here] https://gramanas.github.io/sroa-results.csv
Conclusion
==========
This implies SROA does a pretty good job of preserving debug values.
The DExTer results are not in line with what I've found though. This
might be for a number of reasons. E.g. it could score so low due to
the DebugLoc loss. Also debu...
2018 Apr 27
0
Debugify and Verify-each mode
...ss*es since
> these passes are managed by Function Pass Managers created on the fly
> during *schedulePass()*. I guess we'd have to implement the FunctionPass
> version of Debugify and CheckDebugify.
>
>
> Yes, Anastasis (CC'd) has started exploring this idea:
> https://gramanas.github.io/posts/community-bonding/. Please sync up with
> him before you start hacking, so you can collaborate on the design and
> split up work :). Now that GSoC has officially started, Anastasis needs to
> plan work ahead of time, so we need to find a way to avoid duplicating work.
>...