This is an archive of the discontinued LLVM Phabricator instance.

Differential D129899

Bazel BUILD file for BOLT
ClosedPublic

Authored by tmsriram on Jul 15 2022, 12:55 PM.

Details

Reviewers
brooksmoses
jgorbe
maksfb
rafaelauler
rafauler
Amir
Commits
rG16cccc66b8be: Bazel BUILD file for BOLT.
Summary

Create a Bazel BUILD file for BOLT.

Diff Detail

Event Timeline

tmsriram created this revision.Jul 15 2022, 12:55 PM
Herald added a reviewer: rafauler. · View Herald TranscriptJul 15 2022, 12:55 PM
Herald added a reviewer: Amir. · View Herald Transcript
Herald added a project: Restricted Project. · View Herald Transcript
Herald added a subscriber: ayermolo. · View Herald Transcript
tmsriram requested review of this revision.Jul 15 2022, 12:55 PM
Herald added a subscriber: yota9. · View Herald TranscriptJul 15 2022, 12:55 PM
Harbormaster completed remote builds in B175736: Diff 445110.Jul 15 2022, 1:00 PM
MaskRay added a subscriber: MaskRay.Jul 15 2022, 1:01 PM

Thanks for contributing the Bazel file :) It's probably best to split the atomic rename part to a separate patch.

tmsriram updated this revision to Diff 445124.Jul 15 2022, 1:57 PM

Splitting the changes.

tmsriram added a child revision: D129903: Use std::atomic<std::uint64_t> instead of std::atomic_uint64_t.Jul 15 2022, 2:01 PM
Harbormaster completed remote builds in B175744: Diff 445124.Jul 15 2022, 2:02 PM
brooksmoses accepted this revision.Jul 19 2022, 3:55 PM
This revision is now accepted and ready to land.Jul 19 2022, 3:55 PM
tmsriram edited the summary of this revision. (Show Details)Jul 19 2022, 3:56 PM
jgorbe accepted this revision.Jul 19 2022, 3:57 PM

Looks good to me.

This revision was landed with ongoing or failed builds.Jul 19 2022, 4:06 PM
Closed by commit rG16cccc66b8be: Bazel BUILD file for BOLT. (authored by tmsriram). · Explain Why
This revision was automatically updated to reflect the committed changes.
tmsriram added a commit: rG16cccc66b8be: Bazel BUILD file for BOLT..
Herald added a project: Restricted Project. · View Herald TranscriptJul 19 2022, 4:06 PM
Herald added a subscriber: llvm-commits. · View Herald Transcript
Amir added a comment.Jul 19 2022, 4:56 PM

Thank you for working on it. I was able to build llvm-bolt using the following:

llvm-project/utils/bazel$ bazel build --config=generic_gcc @llvm-project//bolt:llvm-bolt

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?
  2. Is it possible to run check-bolt tests with bazel?
GMNGeoffrey added a subscriber: GMNGeoffrey.Jul 19 2022, 5:04 PM
In D129899#3664216, @Amir wrote:

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?

Yes. In general, there's no way to automatically get the Bazel configuration from the CMake one.

  1. Is it possible to run check-bolt tests with bazel?

Assuming that check-bolt runs lit tests, no. Support for lit tests is not available in the Bazel build. I prototyped something, but couldn't get it working with LLVM's peculiar layer on top of lit that is deeply intertwined with the CMake build. Some more discussion here: https://discourse.llvm.org/t/bazel-and-check-mlir-target-does-bazel-support-running-lit-tests/61898/6?u=gcmn

Amir added a comment.Jul 19 2022, 10:38 PM
In D129899#3664230, @GMNGeoffrey wrote:
In D129899#3664216, @Amir wrote:

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?

Yes. In general, there's no way to automatically get the Bazel configuration from the CMake one.

I see. I know that bazel build is enabled in pre-merge checks but they are flaky at times, and may not trigger for direct pushes. I may look into adding a buildbot configuration with bazel build. If you have any examples of using bazel in buildbot, please let me know.

  1. Is it possible to run check-bolt tests with bazel?

Assuming that check-bolt runs lit tests, no. Support for lit tests is not available in the Bazel build. I prototyped something, but couldn't get it working with LLVM's peculiar layer on top of lit that is deeply intertwined with the CMake build. Some more discussion here: https://discourse.llvm.org/t/bazel-and-check-mlir-target-does-bazel-support-running-lit-tests/61898/6?u=gcmn

Right, it invokes lit underneath. I would assume that you still use cmake build for LLVM testing?

In D129899#3664230, @GMNGeoffrey wrote:
In D129899#3664216, @Amir wrote:

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?

Yes. In general, there's no way to automatically get the Bazel configuration from the CMake one.

  1. Is it possible to run check-bolt tests with bazel?

Assuming that check-bolt runs lit tests, no. Support for lit tests is not available in the Bazel build. I prototyped something, but couldn't get it working with LLVM's peculiar layer on top of lit that is deeply intertwined with the CMake build. Some more discussion here: https://discourse.llvm.org/t/bazel-and-check-mlir-target-does-bazel-support-running-lit-tests/61898/6?u=gcmn

MaskRay added a comment.Jul 19 2022, 10:43 PM
In D129899#3664760, @Amir wrote:
In D129899#3664230, @GMNGeoffrey wrote:
In D129899#3664216, @Amir wrote:

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?

Yes. In general, there's no way to automatically get the Bazel configuration from the CMake one.

I see. I know that bazel build is enabled in pre-merge checks but they are flaky at times, and may not trigger for direct pushes. I may look into adding a buildbot configuration with bazel build. If you have any examples of using bazel in buildbot, please let me know.

  1. Is it possible to run check-bolt tests with bazel?

Assuming that check-bolt runs lit tests, no. Support for lit tests is not available in the Bazel build. I prototyped something, but couldn't get it working with LLVM's peculiar layer on top of lit that is deeply intertwined with the CMake build. Some more discussion here: https://discourse.llvm.org/t/bazel-and-check-mlir-target-does-bazel-support-running-lit-tests/61898/6?u=gcmn

Right, it invokes lit underneath. I would assume that you still use cmake build for LLVM testing?

In D129899#3664230, @GMNGeoffrey wrote:
In D129899#3664216, @Amir wrote:

Couple of questions:

  1. Do I understand it correctly that BUILD.bazel file need to be kept in sync with CMakeLists.txt?

Yes. In general, there's no way to automatically get the Bazel configuration from the CMake one.

  1. Is it possible to run check-bolt tests with bazel?

Assuming that check-bolt runs lit tests, no. Support for lit tests is not available in the Bazel build. I prototyped something, but couldn't get it working with LLVM's peculiar layer on top of lit that is deeply intertwined with the CMake build. Some more discussion here: https://discourse.llvm.org/t/bazel-and-check-mlir-target-does-bazel-support-running-lit-tests/61898/6?u=gcmn

I want to mention the Bazel build is an unofficial build system and keeping it work isn't the community's responsibility.
Keeping it work is appreciated by folks who use the Bazel build, though.

GMNGeoffrey added a comment.Jul 20 2022, 9:26 AM
In D129899#3664760, @Amir wrote:

I see. I know that bazel build is enabled in pre-merge checks but they are flaky at times, and may not trigger for direct pushes. I may look into adding a buildbot configuration with bazel build. If you have any examples of using bazel in buildbot, please let me know.

We have a Buildkite pipeline that builds every commit: https://buildkite.com/llvm-project/upstream-bazel. Alerts are sent to https://groups.google.com/g/llvm-bazel-alerts. See https://github.com/llvm/llvm-project/tree/main/utils/bazel#continuous-testing. You're welcome to build something with the buildbot infrastructure, but I would first look into why pre-merge tests use a different infra than post-merge and what the long-term plan is. There's currently an effort underway to move a bunch of the infra that's currently run by Google directly to instead be under the auspices of the LLVM foundation, Google having donated the necessary GCP credits to do so. See, e.g. https://github.com/llvm/llvm-iwg/issues/112

GMNGeoffrey added a comment.Jul 20 2022, 9:31 AM
In D129899#3664764, @MaskRay wrote:

I want to mention the Bazel build is an unofficial build system and keeping it work isn't the community's responsibility.
Keeping it work is appreciated by folks who use the Bazel build, though.

Yes, thanks for flagging that. @Amir, if you do anything with a build bot, you'd need to ensure it only notifies those that have opted in in some way. I think a patch editing utils/bazel would count as opting in if that patch was in the blame list. There's also the phabricator project people can join. Note how the Bazel pre-merge testing is enabled: https://github.com/llvm/llvm-project/tree/main/utils/bazel#pre-merge-testing

Revision Contents

PathSize
utils/
bazel/
llvm-project-overlay/
bolt/
282 lines

Diff 445974

utils/bazel/llvm-project-overlay/bolt/BUILD.bazel

  • This file was added.
# This file is licensed under the Apache License v2.0 with LLVM Exceptions.
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
package(
default_visibility = ["//visibility:public"],
licenses = ["notice"],
)
cc_binary(
name = "llvm-bolt-heatmap",
srcs = glob([
"tools/heatmap/*.cpp",
]),
deps = [
":Profile",
":Rewrite",
":Utils",
"//llvm:MC",
"//llvm:Object",
"//llvm:Support",
"//llvm:AllTargetsAsmParsers",
"//llvm:AllTargetsDisassemblers",
]
)
cc_binary(
name = "merge-fdata",
srcs = glob([
"tools/merge-fdata/*.cpp",
]),
deps = [
":Profile",
"//llvm:Support",
]
)
cc_binary(
name = "llvm-bolt",
srcs = glob([
"tools/driver/*.cpp",
]),
includes = ["include"],
deps = [
":Profile",
":Rewrite",
":RuntimeLibs",
":Utils",
":TargetX86",
":TargetAArch64",
"//llvm:AllTargetsAsmParsers",
"//llvm:AllTargetsCodeGens",
"//llvm:AllTargetsDisassemblers",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "Rewrite",
srcs = glob([
"lib/Rewrite/*.cpp",
]),
hdrs = glob([
"include/bolt/Rewrite/*.h",
]),
includes = ["include"],
deps = [
":Core",
":Passes",
":Profile",
":RuntimeLibs",
":TargetX86",
":Utils",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DWP",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
"//llvm:ir_headers",
],
)
cc_library(
name = "RuntimeLibs",
srcs = glob([
"lib/RuntimeLibs/*.cpp",
]),
hdrs = glob([
"include/bolt/RuntimeLibs/*.h",
]),
includes = ["include"],
deps = [
":Core",
":Passes",
":Utils",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DWP",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "Profile",
srcs = glob([
"lib/Profile/*.cpp",
]),
hdrs = glob([
"include/bolt/Profile/*.h",
]),
includes = ["include"],
deps = [
":Core",
":Passes",
":Utils",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "Passes",
srcs = glob([
"lib/Passes/*.cpp",
]),
hdrs = glob([
"include/bolt/Passes/*.h",
]),
includes = ["include"],
deps = [
":Core",
":Utils",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
"//llvm:Target",
],
)
cc_library(
name = "TargetX86",
srcs = glob([
"lib/Target/X86/*.cpp",
]),
hdrs = glob([
"lib/Target/X86/*.h",
]),
includes = ["include"],
deps = [
":Core",
"//llvm:X86CommonTableGen",
"//llvm:X86UtilsAndDesc",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DWP",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "TargetAArch64",
srcs = glob([
"lib/Target/AArch64/*.cpp",
]),
hdrs = glob([
]),
includes = ["include"],
deps = [
":Core",
":Utils",
"//llvm:AArch64CommonTableGen",
"//llvm:AArch64UtilsAndDesc",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DWP",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "Core",
srcs = glob([
"lib/Core/*.cpp",
]),
hdrs = glob([
"include/bolt/Core/*.h",
"include/bolt/RuntimeLibs/*.h",
"include/bolt/Passes/*.h",
"include/bolt/Rewrite/*.h",
]),
includes = ["include"],
deps = [
":Utils",
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)
cc_library(
name = "Utils",
srcs = glob([
"lib/Utils/*.cpp",
]),
hdrs = glob([
"include/bolt/Utils/*.h",
]),
includes = ["include"],
deps = [
"//llvm:Analysis",
"//llvm:BinaryFormat",
"//llvm:CodeGen",
"//llvm:DWP",
"//llvm:DebugInfoDWARF",
"//llvm:Demangle",
"//llvm:ExecutionEngine",
"//llvm:MC",
"//llvm:MCDisassembler",
"//llvm:MCParser",
"//llvm:Object",
"//llvm:Support",
],
)