tstellar wrote:
@frederick-vs-ja Were you able to create a PR for this backport?
https://github.com/llvm/llvm-project/pull/140105
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
This was backported in https://github.com/llvm/llvm-project/pull/141004
https://github.com/llvm/llvm-project/pull/140361
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/140381
Fixes #133580
>From abf0d25f2197cb154ec7afd7bca5962975742b44 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 17 May 2025 16:40:51 +
Subject: [PATCH] [CMake][Release] Build with -ffat-lto-objects
Fi
tstellar wrote:
@cor3ntin Were you able to manually create a backport PR for this?
https://github.com/llvm/llvm-project/pull/131811
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
Is there interest in backporting this to the release branch? If so, can
someone manually create a PR?
https://github.com/llvm/llvm-project/pull/127406
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-
tstellar wrote:
@jhuber6 Was the follow-up for this backported too?
https://github.com/llvm/llvm-project/pull/127528
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
Was there a backport PR created for this change?
https://github.com/llvm/llvm-project/pull/137141
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
/cherry-pick f5a30f111dc4ad6422863722eb708059a68a9d5c
https://github.com/llvm/llvm-project/pull/134930
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/134930
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
@AaronBallman Were you able to manually cherry-pick this one?
https://github.com/llvm/llvm-project/pull/135660
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/134434
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar approved this pull request.
LGTM.
https://github.com/llvm/llvm-project/pull/127020
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/127406
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
/cherry-pick f378e52ed3c6f8da4973f97f1ef043c2eb0da721
https://github.com/llvm/llvm-project/pull/127406
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/128554
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/128554
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
/cherry-pick 09832777d830e0fddff84bf36793ec4e453656b0
https://github.com/llvm/llvm-project/pull/128554
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/128788
This will make the binaries more portable.
>From c778a3369e3435b6b08b3ef41c6f628ead50f876 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 25 Feb 2025 23:41:11 +
Subject: [PATCH] [CMake][Release] Sta
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/128090
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
/cherry-pick 148111fdcf0e807fe74274b18fcf65c4cff45d63
https://github.com/llvm/llvm-project/pull/128090
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/128090
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar ready_for_review
https://github.com/llvm/llvm-project/pull/128554
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/128554
This will make the binaries more portable.
>From cd4c3fba2c4edb69797ba16cd6faf1440d5f7e13 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Mon, 24 Feb 2025 19:13:54 +
Subject: [PATCH] [CMake][Release] Sta
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/128274
>From 29b82de7c0ac1cd008a5ddc79c42f5cd492694a7 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 22 Feb 2025 03:08:24 +
Subject: [PATCH 1/3] workflows/release-binaries: Enable Windows x86 builds
---
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/128274
>From 29b82de7c0ac1cd008a5ddc79c42f5cd492694a7 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 22 Feb 2025 03:08:24 +
Subject: [PATCH 1/2] workflows/release-binaries: Enable Windows x86 builds
---
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/128274
None
>From 29b82de7c0ac1cd008a5ddc79c42f5cd492694a7 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 22 Feb 2025 03:08:24 +
Subject: [PATCH] workflows/release-binaries: Enable Windows x86 builds
---
tstellar wrote:
> The fix is NOT correct. You need to enclose in quotes as @tstellar mentions
> in #126876
` llvm_canonicalize_cmake_booleans` converts the string to an integer so you
don't need the quotes now that this function is called with the correct
variable. This is what the generated
https://github.com/tstellar approved this pull request.
LGTM. I confirmed this fixes the release build configuration.
https://github.com/llvm/llvm-project/pull/127967
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
https://github.com/tstellar commented:
I like the idea here. I wonder if this could be generalized somehow in
`add_llvm_library` so that it could be applied to arbitrary libraries. I had
wanted to try to generalize this for executable in `add_llvm_executable`.
I'm fine taking this patch as-
@@ -11,6 +11,7 @@ config.python_exe = "@Python3_EXECUTABLE@"
config.cmake_exe = "@CMAKE_COMMAND@"
config.llvm_src_dir ="@CMAKE_SOURCE_DIR@"
config.cmake_generator ="@CMAKE_GENERATOR@"
+config.use_llvm_build = @CLANG_PGO_TRAINING_USE_LLVM_BUILD@
tstellar wrote:
@@ -574,47 +591,67 @@ def bolt_optimize(args):
opts = parser.parse_args(args)
-output = subprocess.check_output(
-[opts.readelf, "-WS", opts.input], universal_newlines=True
-)
+inputs = opts.input.split(";")
+instrumented_outputs = opts.instrumente
@@ -176,15 +198,15 @@ if (CLANG_BOLT AND NOT LLVM_BUILD_INSTRUMENTED)
TARGET clang POST_BUILD
COMMAND "${Python3_EXECUTABLE}"
${CMAKE_CURRENT_SOURCE_DIR}/../../utils/perf-training/perf-helper.py
bolt-optimize
---method ${CLANG_BOLT}
-
@@ -168,6 +168,28 @@ if (CLANG_BOLT AND NOT LLVM_BUILD_INSTRUMENTED)
)
set(LIT_COMMAND "${lit_base_dir}/${lit_file_name}")
+ set(CLANG_BOLT_INPUTS $)
+ set(CLANG_INSTRUMENTED_OUTPUTS ${CLANG_INSTRUMENTED})
+
+ # Add in dynamically linked libraries, if needs be. Currentl
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/127268
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -90,9 +88,17 @@ else()
set(CLANG_BOOTSTRAP_TARGETS ${LLVM_RELEASE_FINAL_STAGE_TARGETS} CACHE STRING
"")
endif()
+if (LLVM_RELEASE_ENABLE_LTO)
+ # Enable LTO for the runtimes. We need to configure stage1 clang to default
+ # to using lld as the linker because the stage
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/8] [CMake][Release] Statically link clang with stage1
runtimes
tstellar wrote:
@philnik777 Were you able to manually create the backport pull request?
https://github.com/llvm/llvm-project/pull/123678
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/8] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/7] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/7] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/6] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/5] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/3] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/127268
>From a705acfd439e6310648b0ed1ad612eaffc408ad5 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 14 Feb 2025 17:46:25 +
Subject: [PATCH 1/2] [CMake][Release] Statically link clang with stage1
runtimes
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/127268
This change will cause clang and the other tools to statically link against the
runtimes built in stage1. This will make the built binaries more portable by
eliminating dependencies on system libraries like l
tstellar wrote:
@petrhosek I also wanted to mention, if you are interested in upstreaming this
minimal corpus, I would support making it the default instead of the current
llvm-support build.
https://github.com/llvm/llvm-project/pull/126876
___
cfe-
https://github.com/tstellar approved this pull request.
https://github.com/llvm/llvm-project/pull/126768
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar approved this pull request.
LGTM.
https://github.com/llvm/llvm-project/pull/126876
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/124870
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/119896
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
> These cache files seem to be largely the same as
> [PGO.cmake](https://github.com/llvm/llvm-project/blob/4cec0ba92955c353c52efe728b2cfef3fbdf60f8/clang/cmake/caches/PGO.cmake),
>
> [PGO-stage2.cmake](https://github.com/llvm/llvm-project/blob/04b002bbb838bc502bd6d5f602af95efd6
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/117802
>From 3bddb3c6d25efbfcc901a42a8367be85599d1f7e Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Mon, 23 Sep 2024 13:34:46 +
Subject: [PATCH 1/8] [CMake] Add a cache file for building a highly-optimized
LL
@@ -0,0 +1,17 @@
+# Stage 1
+# * Build an LTO optimized libcxx, so we can staticially link it into stage 2
+# clang.
+
+
+set(CMAKE_BUILD_TYPE Release CACHE STRING "")
+set(LLVM_TARGETS_TO_BUILD Native CACHE STRING "")
+set(LLVM_ENABLE_RUNTIMES "compiler-rt;libcxx;libcxxabi;libu
@@ -0,0 +1,17 @@
+# Stage 1
+# * Build an LTO optimized libcxx, so we can staticially link it into stage 2
+# clang.
+
+
+set(CMAKE_BUILD_TYPE Release CACHE STRING "")
+set(LLVM_TARGETS_TO_BUILD Native CACHE STRING "")
+set(LLVM_ENABLE_RUNTIMES "compiler-rt;libcxx;libcxxabi;libu
@@ -44,7 +44,7 @@ jobs:
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 #
v4.1.1
- name: Setup ccache
-uses: hendrikmuhs/ccache-action@v1
+uses:
hendrikmuhs/ccache-action@ed74d11c0b343532753ecead8a951bb09bb34bc9 # v1.2
--
@@ -0,0 +1,17 @@
+# Stage 1
+# * Build an LTO optimized libcxx, so we can staticially link it into stage 2
+# clang.
+
+
+set(CMAKE_BUILD_TYPE Release CACHE STRING "")
+set(LLVM_TARGETS_TO_BUILD Native CACHE STRING "")
+set(LLVM_ENABLE_RUNTIMES "compiler-rt;libcxx;libcxxabi;libu
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/117802
>From 3bddb3c6d25efbfcc901a42a8367be85599d1f7e Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Mon, 23 Sep 2024 13:34:46 +
Subject: [PATCH 1/4] [CMake] Add a cache file for building a highly-optimized
LL
https://github.com/tstellar approved this pull request.
https://github.com/llvm/llvm-project/pull/118309
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
This looks fine.
https://github.com/llvm/llvm-project/pull/118309
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/120777
>From cb87398ea7f654559799ff7f79f292842832c29c Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Wed, 20 Nov 2024 20:59:38 -0800
Subject: [PATCH 01/12] Workflows: Use new depot runners for x86 Linux release
bu
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 01/10] [clang][cmake] Apply bolt optimizations as part of the
cla
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 1/7] [clang][cmake] Apply bolt optimizations as part of the
clang
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 1/6] [clang][cmake] Apply bolt optimizations as part of the
clang
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 1/4] [clang][cmake] Apply bolt optimizations as part of the
clang
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 1/3] [clang][cmake] Apply bolt optimizations as part of the
clang
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119896
>From dd1f6807904691586c715d447fff54915a46c751 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Tue, 3 Dec 2024 22:32:46 +
Subject: [PATCH 1/2] [clang][cmake] Apply bolt optimizations as part of the
clang
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/119896
This change removes the need to call the clang-bolt target in order to apply
bolt optimizations to clang. Now running `ninja clang` will build a clang with
bolt optimizations, and `ninja check-clang` and `nin
@@ -20,9 +21,13 @@ elif clang_bolt_mode == "perf":
else:
assert 0, "Unsupported CLANG_BOLT_MODE variable"
-config.clang = perf_wrapper + os.path.realpath(
+clang_nowrapper = os.path.realpath(
lit.util.which(clang_binary, config.clang_tools_dir)
).replace("\\", "/")
+
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/119117
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119117
>From 5d13b69039fab7c5960288cead18dc76f5d01f4f Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Thu, 5 Dec 2024 15:01:27 +
Subject: [PATCH 1/5] [clang][perf-training] Fix profiling with
-DCLANG_BOLT=perf
https://github.com/tstellar edited
https://github.com/llvm/llvm-project/pull/119117
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119117
>From 5d13b69039fab7c5960288cead18dc76f5d01f4f Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Thu, 5 Dec 2024 15:01:27 +
Subject: [PATCH 1/4] [clang][perf-training] Fix profiling with
-DCLANG_BOLT=perf
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119117
>From 5d13b69039fab7c5960288cead18dc76f5d01f4f Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Thu, 5 Dec 2024 15:01:27 +
Subject: [PATCH 1/3] [clang][perf-training] Fix profiling with
-DCLANG_BOLT=perf
tstellar wrote:
@aaupov When we build llvm-support there is one perf.data file generate for
each cpp file compiled, so we end up without about 150 files. Is there some
way to merge those together before running perf2bolt?
https://github.com/llvm/llvm-project/pull/119117
__
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/119117
>From 5d13b69039fab7c5960288cead18dc76f5d01f4f Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Thu, 5 Dec 2024 15:01:27 +
Subject: [PATCH] [clang][perf-training] Fix profiling with -DCLANG_BOLT=perf
This
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/119117
This fixes the llvm-support build that generates the profile data. However, I'm
wondering if maybe we should disable llvm-suppot and only run hello-world with
-DCLANG_BOLT=perf. The bolt optimizations with pe
tstellar wrote:
/cherry-pick 18af3fc1bf8855e1e166e64a9210ed07d610aa54
https://github.com/llvm/llvm-project/pull/118978
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar milestoned
https://github.com/llvm/llvm-project/pull/118978
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/118978
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/118978
The first path argument was always being ignored, and since most calls to this
command only passed one path, it wasn't actually doing anything in most cases.
This bug was introduced by dd0356d741aefa25ece973d6
tstellar wrote:
> Well, we're currently approaching this from the angle of "expose everything
> and then the user can do whatever they want", but perhaps the discussion we
> should be having is "what use cases do we explicitly want to support?" and
> then we write plugins to demonstrate that w
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/117802
>From 3bddb3c6d25efbfcc901a42a8367be85599d1f7e Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Mon, 23 Sep 2024 13:34:46 +
Subject: [PATCH 1/2] [CMake] Add a cache file for building a highly-optimized
LL
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/117802
The goal of these cache files is to provide a toolchain that:
1. Relies on only LLVM components (as much as possible).
2. Is highly optimized.
These cache files will produce a full toolchain
(clang/compiler-rt
tstellar wrote:
@aaronpuchert That looks fine to me.
https://github.com/llvm/llvm-project/pull/116556
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar approved this pull request.
This LGTM. I'm fine taking this version instead of my patch.
https://github.com/llvm/llvm-project/pull/116556
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bi
https://github.com/tstellar commented:
So is the sign function currently implemented in the OpenCL headers?
https://github.com/llvm/llvm-project/pull/115699
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/111625
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tstellar wrote:
Is there any reason why the tool should be in the monorepo and not some other
repository?
Also, as for keeping the annotations up-to-date. My recommendation is to add a
github action job that runs the ids tool and then submits a pull request for
any necessary changes. We co
tstellar wrote:
Any other comments on this one? If not, I think I'll merge it after the dev
meeting.
https://github.com/llvm/llvm-project/pull/111625
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
@@ -0,0 +1,2 @@
+RUN: %cmake -G %cmake_generator -B %t -S %llvm_src_dir
-DCMAKE_C_COMPILER=%clang -DCMAKE_CXX_COMPILER=%clang
-DCMAKE_CXX_FLAGS="--driver-mode=g++" -DCMAKE_BUILD_TYPE=Release
tstellar wrote:
The current bolt.lit.cfg substitutes `%clang_cpp` to `
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/111625
>From 40efbcf0fd348625c892453d915eb7601adda917 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 5 Oct 2024 17:17:33 +
Subject: [PATCH 1/2] [Clang][perf-training] Do build of libLLVMSupport for
perf t
tstellar wrote:
> I'm assuming you used instrumented BOLT here? Also, do you have numbers on
> how long the perf training took?
Yes, it was instrumented BOLT. I've added the perf training times to the commit
summary.
https://github.com/llvm/llvm-project/pull/111625
_
https://github.com/tstellar edited
https://github.com/llvm/llvm-project/pull/111625
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/111625
This adds a build of the libLLVMSupport to the lit suite that is used for
generating profile data. This helps to improve both PGO and BOLT optimization
of clang over the existing hello world training program.
https://github.com/tstellar created
https://github.com/llvm/llvm-project/pull/110758
We do the same thing for libLLVM.so. This should help avoid issues when an
applications loads two different versions of the library at the same time.
>From 59673ed97d92df34d6f662da5a51f6e28806b5af Mon Sep 17
tstellar wrote:
@keith Yes, this change needs to be in the release branch or it won't take
effect.
https://github.com/llvm/llvm-project/pull/109909
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo
@@ -109,3 +109,6 @@ set_final_stage_var(LLVM_ENABLE_PROJECTS
"${LLVM_RELEASE_ENABLE_PROJECTS}" STRIN
set_final_stage_var(CPACK_GENERATOR "TXZ" STRING)
set_final_stage_var(CPACK_ARCHIVE_THREADS "0" STRING)
+if(${CMAKE_HOST_SYSTEM_NAME} MATCHES "Darwin")
+ set_final_stage_var(
tstellar wrote:
If you add these 3 options to the cmake invocation in release-binaries.yml, it
should give us more verbose output and make the problem easier to debug:
```
-DCMAKE_VERBOSE_MAKEFILE=ON \
-DBOOTSTRAP_CMAKE_VERBOSE_MAKEFILE=ON \
-DBOOTSTRAP_BOOTSTRAP_CMAKE_V
tstellar wrote:
You want to be downloading and testing this artifact:
https://github.com/llvm/llvm-project/pull/109909
___
cfe-commits mailing list
cfe-commits@
https://github.com/tstellar approved this pull request.
This looks good to me. It looks like we need to add the Release.cmake file to
the list of files that trigger the release-binaries-all test, but that can be
done in another PR.
https://github.com/llvm/llvm-project/pull/109909
1 - 100 of 548 matches
Mail list logo
