Status Update
Comments
ry...@google.com <ry...@google.com> #3
We have to disable applying patches from patch_manager for this revision and all following revisions. This is easily added as a hack to cros-llvm.eclass
ki...@google.com <ki...@google.com> #4
Bugjuggler: crrev/c/5902466 -> fixed
ry...@google.com <ry...@google.com> #5
ki...@google.com <ki...@google.com> #6
whoops, wrong bug
ry...@google.com <ry...@google.com> #7
Project: chromiumos/overlays/chromiumos-overlay
Branch: main
Author: Jordan R Abrahams-Whitehead <
Link:
eclass: Don't patch LLVM with new branch workflows
Expand for full commit details
eclass: Don't patch LLVM with new branch workflows
There's no particularly easy way to extract whether
we're on a specific sha with the manifest, or whether
we're on an upstream branch. The easiest way seems to
be to just say later versions use this new workflow.
BUG=b:368393962
TEST=sudo emerge sys-devel/llvm on new branch
TEST=CQ
Change-Id: I8cbc5c620d3ba429576b6cba02f761760e2e5ceb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5905716
Commit-Queue: Jordan Abrahams-Whitehead <ajordanr@google.com>
Tested-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
Files:
- M
eclass/cros-llvm.eclass
Hash: f553966e5e54820caa194785da5cbd5335976cc3
Date: Mon Oct 07 19:40:07 2024
gb...@google.com <gb...@google.com> #8
Project: chromiumos/third_party/toolchain-utils
Branch: main
Author: Jordan R Abrahams-Whitehead <
Link:
llvm_tools: Add --keep-non-patch for git_am calls
Expand for full commit details
llvm_tools: Add --keep-non-patch for git_am calls
We want to preserve the leading tags like [libc++] and
[lldb], and this flag lets us do that.
BUG=b:368393962
TEST=Applied patch stack and uploaded
Change-Id: Ic452e4c0a03291dd6530f0c23bead9a6a883d470
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/5923000
Commit-Queue: George Burgess <gbiv@chromium.org>
Auto-Submit: Jordan Abrahams-Whitehead <ajordanr@google.com>
Tested-by: George Burgess <gbiv@chromium.org>
Tested-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
Commit-Queue: ChromeOS Auto Runner <chromeos-auto-runner@chromeos-bot.iam.gserviceaccount.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
Files:
- M
llvm_tools/patch_utils.py
Hash: 729fc0df0e556eda0fbbcecd905b3a8ab347ac55
Date: Thu Oct 10 21:33:42 2024
Description
Go binaries are not supported in CrOS at this time for releases.
However, it is widely utilized in testing, provisioning, and SDK build tools.
It would be advantageous to devise a method of stripping these symbol tables after the build process to reduce the disk footprint on test images (only at this time), but still provide the ability to debug by locating the symbol tables.
I am reaching out to the toolchain team for assistance!