https://github.com/NuriAmari updated
https://github.com/llvm/llvm-project/pull/65179:
>From 5d395c85b84e5a554df4b092014d38123e666c6c Mon Sep 17 00:00:00 2001
From: Nuri Amari
Date: Tue, 29 Aug 2023 10:10:57 -0700
Subject: [PATCH 1/2] Add flags to dump IR to a file before and after LLVM
passes
https://github.com/NuriAmari updated
https://github.com/llvm/llvm-project/pull/65179:
>From 5d395c85b84e5a554df4b092014d38123e666c6c Mon Sep 17 00:00:00 2001
From: Nuri Amari
Date: Tue, 29 Aug 2023 10:10:57 -0700
Subject: [PATCH 1/3] Add flags to dump IR to a file before and after LLVM
passes
https://github.com/NuriAmari updated
https://github.com/llvm/llvm-project/pull/65179:
>From 5d395c85b84e5a554df4b092014d38123e666c6c Mon Sep 17 00:00:00 2001
From: Nuri Amari
Date: Tue, 29 Aug 2023 10:10:57 -0700
Subject: [PATCH 1/4] Add flags to dump IR to a file before and after LLVM
passes
@@ -0,0 +1,71 @@
+; RUN: mkdir -p %t/logs
+; RUN: rm -rf %t/logs
+
+; Basic dump before and after a single module pass
+; RUN: opt %s -disable-output -passes='no-op-module' -ir-dump-directory
%t/logs -dump-after=no-op-module -dump-before=no-op-module
+; RUN: find %t/logs -type f
NuriAmari wrote:
I've tried this on a real application, and the output paths quickly get
extremely long. So long that we fail to create the directory structure. Perhaps
the nesting idea isn't the right choice after all.
https://github.com/llvm/llvm-project/pull/65179
__
https://github.com/NuriAmari closed
https://github.com/llvm/llvm-project/pull/65179
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
NuriAmari wrote:
> What about an option that just redirects the PrintIRInstrumentation output to
> files instead of stderr? The files can be something like `$N-$modulename.ll`
> where `$N` is an int that increments.
Yeah that's more or less what I'm working on now. My plan is:
- Add a flag th