Displaying 20 results from an estimated 5000 matches similar to: "Passes to add/validate synthetic debug info"
2017 Nov 28
2
RFC: [GlobalISel] Towards a generic MI combiner framework
Thanks for the suggestions Vedant. Synthetic debug info is an interesting idea that sounds worthwhile. Could this be implemented as a “wrapper” pass that automatically decorates debug info before and after a specific pass run in opt (or pipeline of passes)? It might be useful to be able to easily enable this for a wide range of tests without having to manually modify each run line, perhaps as an
2018 Apr 26
2
Debugify and Verify-each mode
Hello,
> On Apr 26, 2018, at 6:44 AM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> 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 {
>
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 ?
>
>
2017 Dec 04
2
[RFC] - Deduplication of debug information in linkers (LLD)
At least one proprietary linker put a lot of effort into deduplicating and
rewriting debug information. This took up the majority of the link time
despite serious engineering time on performance optimisation. For example,
some sections were written from scratch by the linker because that proved
faster than parsing the input. Teaching LLD to dedup DWARF should be
expected to dramatically slow it
2018 Mar 16
0
Debugify and Verify-each mode
> 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 ?
No, there's no reserved work. If you'd like to work on this I encourage you to do so. There's plenty of other work slated for the GSoC project.
2018 Apr 27
0
Debugify and Verify-each mode
Hello,
@Anastasis: what do you think about this? Do you mind if I implement the
debugify-each mode and refactor the code to have DebugifyFunctionPass and
DebugifyLoopPass? I am sorry if it bothers you, I should have done this
earlier, so you could focus on fixing the optimization passes. FYI, my
debugify-each
is quite ready, I am having Debugify and CheckDebugify before and after
each ModulePass,
2017 Nov 18
2
RFC: [GlobalISel] Towards a generic MI combiner framework
> On Nov 13, 2017, at 11:53 AM, Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi Amara,
>
>> On Nov 10, 2017, at 9:12 AM, Amara Emerson via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>> Hi everyone,
>>
>> This RFC concerns the design and architecture of a generic machine
2018 Mar 16
2
Debugify and Verify-each mode
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 ?
However, if I understand correctly, we do not want to take the output of
the first check-debugify (I mean the .ll file with potentially all the
WARNINGs and ERRORs after the first pass) as input for the second debugify.
What we need is to take the fresh output of
2020 Jun 18
2
[DebugInfo] RFC: Introduce LLVM DI Checker utility
Hi Vedant,
Thanks a lot for your comments!
>It looks like a lot of the new infrastructure introduced here
<https://github.com/djolertrk/llvm-di-checker/commit/9d26ac2557c584f6cf82ac5535fc47f8bd267a27> consists
of logic copied from the debugify implementation. Why is introducing a
new pair of passes better than extending the ones we have? The core
infrastructure needed to track
2018 Mar 14
2
Debugify and Verify-each mode
Hi Vedant, hi all,
My goal is to measure debug info loss of *each* optimization pass in LLVM.
I am trying to create a debugify-each mode in opt, inspired by
verify-each mode which is supposed to already work.
However, if I understand correctly, the verify-each mode (triggered by
-verify-each option in opt) only works when we provide a pass list or a
pass pipeline. Is this intended? I mean, why
2018 Mar 15
0
Debugify and Verify-each mode
Hi Son Tuan,
Thanks for taking a look at this :). Responses inline --
> On Mar 14, 2018, at 8:11 AM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> Hi Vedant, hi all,
>
> My goal is to measure debug info loss of each optimization pass in LLVM. I am trying to create a debugify-each mode in opt, inspired by verify-each mode which is supposed to already work.
+
2018 Feb 05
0
Debuggability of -O1 level
Hello Paul, François and Vedant,
Thank you all for your answers. And sorry for this late reply. I wanted to
dig more into the LLVM source code to get a better understanding of the
debug part of it before replying/asking more questions.
I have came across this
https://llvm.org/docs/SourceLevelDebugging.html#debugging-optimized-code
which stated that
"*Basically, the debug information allows
2018 Jan 29
2
Debuggability of -O1 level
Hi,
I'm not sure which passes exactly drop debug info, but it's likely that most of them do. If you're interested in working on this problem, I suggest experimenting with the debugify utility in opt. This tool can be used to identify passes which drop debug info and to generate targeted/reduced test cases for specific problems. To use it, you can add the '-enable-debugify'
2020 Jun 17
4
[DebugInfo] RFC: Introduce LLVM DI Checker utility
Hi,
I am sharing the proposal [0] which gives a brief introduction for the
implementation of the LLVM DI Checker utility. On a very high level, it
is a pair of LLVM (IR) Passes that check the preservation of the
original debug info in the optimizations. There are options controlling
the passes, that could be invoked from ``clang`` as well as from ``opt``
level.
By testing the utility on the
2018 Apr 20
2
LLVM Pass Managers
Hi Vedant,
Thanks for your reply. More comments inline.
Son Tuan Vu
On Fri, Apr 20, 2018 at 10:19 PM, Vedant Kumar <vsk at apple.com> wrote:
> Hi,
>
> + Chandler, who has a lot more experience with our pass managers.
>
> On Apr 20, 2018, at 12:56 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> + Vedant: what do you think about the last point, since
2018 Jan 29
2
Debuggability of -O1 level
My experience is that just running mem2reg (while disabling virtually all
other passes ) in O1 will substantially improve debuggability while giving
acceptable performance.
On Mon, Jan 29, 2018 at 11:39 AM, via llvm-dev <llvm-dev at lists.llvm.org>
wrote:
> (Remembering to +llvm-dev this time…)
>
>
>
> There has been some progress in the direction of improving debuggability
2018 Apr 20
0
LLVM Pass Managers
> On Apr 20, 2018, at 1:46 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> Hi Vedant,
>
> Thanks for your reply. More comments inline.
>
> Son Tuan Vu
>
> On Fri, Apr 20, 2018 at 10:19 PM, Vedant Kumar <vsk at apple.com <mailto:vsk at apple.com>> wrote:
> Hi,
>
> + Chandler, who has a lot more experience with our pass managers.
2018 Apr 20
0
LLVM Pass Managers
Hi,
+ Chandler, who has a lot more experience with our pass managers.
> On Apr 20, 2018, at 12:56 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote:
>
> + Vedant: what do you think about the last point, since Debugify is also related?
Could you clarify the question? I'm not sure what it is you'd like me to chime in about.
> 2, I've asked this question once but
2018 Apr 20
2
LLVM Pass Managers
+ Vedant: what do you think about the last point, since Debugify is also
related?
Son Tuan Vu
On Thu, Apr 19, 2018 at 6:14 PM, Philip Pfaffe <philip.pfaffe at gmail.com>
wrote:
> Hi Son,
>
> PassManagerBuilder is used to populate legacy PassManagers. That role is
> taken over by PassBuilder for new-PM passes.
>
> Cheers,
> Philip
>
> 2018-04-18 13:40 GMT+02:00