https://github.com/jhuber6 commented:
Shouldn't we be able to just use LTO after the SPIR-V backend left experimental?
https://github.com/llvm/llvm-project/pull/133797
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-ppc64-aix` running
on `aix-ppc64` while building `clang` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/64/builds/2733
Here is the relevant piece of the build lo
https://github.com/asudarsa created
https://github.com/llvm/llvm-project/pull/133797
This PR has the following changes:
Replace llvm-link with calls to linkInModule to link device files Add
-print-linked-module option to dump linked module for testing Added a test to
verify that linking is wo
https://github.com/asudarsa updated
https://github.com/llvm/llvm-project/pull/133797
>From 675595e453b2452e49847ba3b949909367c7942a Mon Sep 17 00:00:00 2001
From: Arvind Sudarsanam
Date: Mon, 31 Mar 2025 13:04:47 -0700
Subject: [PATCH 1/2] [clang-sycl-linker] Replace llvm-link with API calls
T
asudarsa wrote:
@jhuber6
Can you please take a look? This is one of the many changes we are making to
upstream SYCL.
Thanks
https://github.com/llvm/llvm-project/pull/133797
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.
asudarsa wrote:
> Shouldn't we be able to just use LTO after the SPIR-V backend left
> experimental?
Hi @jhuber6
Thanks for the ping back. That is the eventual path for us. However, we would
like to do it in stages. Replacing llvm-link tool with linkInModule call helps
us to achieve one of
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Arvind Sudarsanam (asudarsa)
Changes
This PR has the following changes:
Replace llvm-link with calls to linkInModule to link device files Add
-print-linked-module option to dump linked module for testing Added a test to
verify that linki
