bazel: add debug/sanitizer configs and expand build documentation by napetrov · Pull Request #3538 · uxlfoundation/oneDAL

napetrov · 2026-02-25T00:24:25Z

Summary

Addresses BLOCKER 5 and BLOCKER 6 from #3530.

BLOCKER 5: Build options parity with Make

Adds .bazelrc configurations matching Make REQDBG / REQSAN options:

Make option	Bazel equivalent	Notes
`REQDBG=1`	`--config=dbg`	debug symbols + assertions
`REQDBG=symbols`	`--config=dbg-symbols`	debug symbols only
`REQSAN=address`	`--config=asan`	AddressSanitizer
`REQSAN=static`	`--config=asan-static`	ASan, static libasan
`REQSAN=thread`	`--config=tsan`	ThreadSanitizer
`REQSAN=undefined`	`--config=ubsan`	UBSan
`COPT=-flag`	`--copt=-flag`	custom compiler flag

Example usage:

# Debug build with assertions (equivalent to Make REQDBG=1)
bazel test //cpp/oneapi/dal:tests --config=dbg

# ASan (equivalent to Make REQSAN=address)
bazel test //cpp/oneapi/dal:tests --config=asan --config=dbg

# Custom flag (equivalent to Make COPT=-flag)
bazel build //:release --copt=-march=native

BLOCKER 6: Build documentation

Expands dev/bazel/README.md with:

Debug and sanitizer builds section
Release build section (ISA variants, DPC++ option)
Custom compiler/linker flags section
Make → Bazel flag reference table

Changes

.bazelrc: new dbg, dbg-symbols, asan, asan-static, tsan, ubsan configs
dev/bazel/README.md: new sections appended to existing guide

Testing

No functional code changes — configuration and documentation only.

--config=dbg uses existing toolchain dbg_compile_flags (-g already wired in cc_toolchain_lnx.bzl).
enable_assert flag already connected to ONEDAL_ENABLE_ASSERT / DEBUG_ASSERT defines.

Part of #3530.

Copilot

Pull request overview

This PR aims to improve Bazel/Make parity for developer builds by adding debug/sanitizer Bazel configs, enforcing “full ISA” behavior for //:release, and expanding Bazel build documentation.

Changes:

Adds .bazelrc named configs for debug and common sanitizers (ASan/TSan/UBSan) and documents Make → Bazel flag mappings.
Introduces a Starlark transition to make //:release build all ISA variants by default (when --cpu is left at auto), and updates CI to build a single ISA.
Adds an ISA coverage shell test script and wires it into Bazel as a manual sh_test.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
`.bazelrc`	Adds Bazel named configs for dbg/sanitizers and documents custom flag usage
`dev/bazel/README.md`	Expands Bazel build documentation (debug/sanitizers, release, flag mapping)
`dev/bazel/release.bzl`	Adds a CPU build-setting transition for `//:release` library dependencies
`dev/bazel/tests/isa_coverage_test.sh`	New script to validate ISA-dispatch symbol presence in `libonedal_core.so`
`dev/bazel/tests/BUILD`	Exports Bazel test scripts from `dev/bazel/tests` package
`cpp/daal/BUILD`	Adds a manual `sh_test` target to run the ISA coverage script on `:core_dynamic`
`dev/bazel/dal.bzl`	Extends module macro to accept `copts` and sets visibility/export-related defines
`dev/bazel/daal.bzl`	Extends module macro to accept `copts` and sets visibility/export-related defines
`.github/workflows/docker-validation-nightly.yml`	CI builds `:release` for `avx2` only for speed

Copilot · 2026-02-25T00:34:02Z

dev/bazel/tests/BUILD

+    "mkl_linkage_test.sh",
+    "isa_coverage_test.sh",
+])


exports_files() lists mkl_linkage_test.sh, but this file does not exist under dev/bazel/tests/ in the PR. Bazel will fail to load this package. Either add the script or remove it from exports_files().

Suggested change

"mkl_linkage_test.sh",

"isa_coverage_test.sh",

])

"isa_coverage_test.sh",

])

Copilot · 2026-02-25T00:34:02Z

dev/bazel/release.bzl

        "include_prefix": attr.string_list(),
        "include_skip_prefix": attr.string_list(),
-        "lib": attr.label_list(allow_files=True),
+        "lib": attr.label_list(allow_files=True, cfg=_release_cpu_all_transition),


This rule now uses a Starlark configuration transition (cfg=_release_cpu_all_transition), but the rule doesn’t declare the required _allowlist_function_transition attribute. On Bazel 9 this typically causes analysis to fail with a transition allowlist error; add the allowlist attr to _release’s attrs.

Suggested change

"lib": attr.label_list(allow_files=True, cfg=_release_cpu_all_transition),

"lib": attr.label_list(allow_files=True, cfg=_release_cpu_all_transition),

"_allowlist_function_transition": attr.label(

default = "@bazel_tools//tools/allowlists/function_transition_allowlist",

),

Copilot · 2026-02-25T00:34:03Z

dev/bazel/tests/isa_coverage_test.sh

+    count=$(nm -D "${LIB}" | grep -c "${cpu_type}" || true)
+    if [[ "${count}" -gt 0 ]]; then
+        echo "  OK  ${isa_name} (${cpu_type}): ${count} dispatch symbols"


nm failures can leave count empty (e.g., if nm isn’t available), and then [[ "${count}" -gt 0 ]] errors under set -e. Consider explicitly handling the nm-missing/error case (e.g., default count to 0 or check command -v nm).

Copilot · 2026-02-25T00:34:03Z

dev/bazel/tests/isa_coverage_test.sh

+        echo "  FAIL ${isa_name} (${cpu_type}): 0 dispatch symbols found"
+        echo "       Build with --cpu=all or --config=release to include all ISAs"
+        FAIL=$((FAIL + 1))


The failure hint mentions --config=release, but this repo doesn’t define a release config in .bazelrc. Suggest updating the message to point to the supported flags (--cpu=all or building //:release).

Copilot · 2026-02-25T00:34:03Z

dev/bazel/README.md

+```sh
+bazel build //:release --config=dbg
+bazel test //cpp/oneapi/dal:tests --config=dbg
+```


The guide recommends bazel test ... --config=dbg/asan/..., but .bazelrc only defines build:dbg, build:asan, etc. To ensure the configs apply to bazel test as documented, add matching test:<config> stanzas (or move these options under common:<config>).

Copilot · 2026-02-25T00:34:03Z

dev/bazel/README.md

+> Note: Not all compilers support all sanitizers. GCC will fail with
+> `REQSAN=memory` by design. Use icpx or clang for memory sanitizer.


The note references Make’s REQSAN=memory, but this is the Bazel guide and there is no corresponding Bazel config/flag shown here. Consider rephrasing in terms of Bazel/clang flags (e.g., -fsanitize=memory) or explicitly documenting that msan isn’t currently wired as a --config.

Suggested change

> Note: Not all compilers support all sanitizers. GCC will fail with

> `REQSAN=memory` by design. Use icpx or clang for memory sanitizer.

> Note: Not all compilers support all sanitizers. In the Make-based flow,

> MemorySanitizer corresponds to `REQSAN=memory`, but there is currently no

> Bazel `--config` preset for msan. To use MemorySanitizer with Bazel you must

> use a compiler that supports it (such as icpx or clang) and pass the

> appropriate flags (for example, `--copt=-fsanitize=memory` and related msan

> options). GCC does not support MemorySanitizer and will fail by design.

Copilot · 2026-02-25T00:34:04Z

dev/bazel/README.md

+The `//:release` target automatically compiles all ISA variants regardless of
+the `--cpu` flag default. To restrict ISA coverage (e.g., for faster CI):
+


This claim is a bit stronger than what the transition implements: release.bzl only forces --cpu=all when the cpu build setting is auto; if a user sets --cpu=avx2 in a personal .bazelrc, //:release will not build all ISAs. Suggest updating the wording to reflect that it forces all ISAs only when --cpu is left as auto (unset).

Copilot · 2026-02-25T00:34:04Z

.bazelrc

+# Adds: -g debug symbols only
+#   bazel build //:release --config=dbg-symbols
+build:dbg-symbols \
+    --compilation_mode=dbg


build:dbg-symbols sets --compilation_mode=dbg, but this toolchain’s dbg feature already adds assertion-related defines (see dev/bazel/toolchains/cc_toolchain_lnx.bzl dbg compile flags). That makes dbg-symbols behave like “debug + asserts”, not “symbols only” as documented. Consider keeping -c opt and only adding -g (and avoiding --enable_assert) for the symbols-only config.

Suggested change

--compilation_mode=dbg

--copt=-g \

--cxxopt=-g \

--linkopt=-g

Copilot · 2026-02-25T00:34:04Z

.bazelrc

+    --linkopt=-fsanitize=address \
+    --linkopt=-shared-libasan


build:asan unconditionally adds -shared-libasan. In Make, this flag is compiler-dependent and is intentionally empty for GCC (dev/make/compiler_definitions/gnu.mk), so using it unconditionally can break the documented CC=gcc bazel ... workflow. Consider dropping -shared-libasan (GCC defaults to shared) or gating it by compiler/toolchain.

Suggested change

--linkopt=-fsanitize=address \

--linkopt=-shared-libasan

--linkopt=-fsanitize=address

napetrov · 2026-02-25T03:45:53Z

Addressed all Copilot review comments:

dbg-symbols: replaced --compilation_mode=dbg with --copt=-g --cxxopt=-g — avoids unwanted assertions and -O0, keeps optimization
asan: removed -shared-libasan — breaks GCC (compiler picks the right default)
All debug/sanitizer configs: switched from build: to common: — now applies uniformly to both bazel build and bazel test
README msan note: rephrased entirely in Bazel terms, removed Make REQSAN=memory reference, added manual flag example
ISA transition wording: clarified that //:release forces all ISAs only when --cpu=auto (default); explicit --cpu values are respected

Comments on dev/bazel/tests/BUILD, dev/bazel/release.bzl, and dev/bazel/tests/isa_coverage_test.sh are from a previous (now-removed) revision — those files are not part of this PR.

david-cortes-intel · 2026-02-25T07:17:46Z

When sanitizers are added, debugging symbols should also be added.
It's missing some important sanitizers: memory, type.
- Some sanitizers are only supported by clang.
For DPC, the sanitizer flags would be different. There might be some work around adding DPC sanitizers in a PR from @Alexandr-Solovev .
I get the impression from this PR that it's not possible to enable assertions with sanitizers.
It's also useful to enable assertions from the standard library, like bounds checks on std::vector, which are handled through C-preprocessor arguments.

napetrov · 2026-02-25T23:41:58Z

I've already cleaned up the dev/bazel/tests/BUILD references in the latest commits (the file itself is no longer part of this PR). This was addressed previously.

david-cortes-intel · 2026-02-26T07:41:02Z

dev/bazel/README.md

+
+## Custom Compiler and Linker Flags
+
+Equivalent to Make `COPT` / `CXXFLAGS`. Pass via `--copt` and `--linkopt`:


Bazel docs mention to use cxxopt when they are C++ flags:

Fixed in 04b6db8: updated README to use --cxxopt for C++-only flags (e.g. -D_GLIBCXX_DEBUG) and --copt for flags that apply to both C and C++. Added explicit distinction in both the section text and the ~/.bazelrc examples.

Fixed in 04b6db8: README now distinguishes --copt (C+C++) from --cxxopt (C++-only) and updates examples accordingly.

david-cortes-intel · 2026-02-26T07:42:28Z

dev/bazel/README.md

+> `--config=msan` preset. To use MemorySanitizer, use a compiler that supports
+> it (icpx or clang) and pass flags manually:
+> ```sh
+> bazel test //cpp/oneapi/dal:tests --copt=-fsanitize=memory --linkopt=-fsanitize=memory


Should also use -fsanitize-memory-track-origins.

Added in a5f1714: msan config now includes -fsanitize-memory-track-origins.

david-cortes-intel · 2026-02-26T07:43:05Z

dev/bazel/README.md

+bazel build //:release --config=dbg-symbols
+```
+
+> Note: The `libonedal_dpc.so` library does not support debug mode due to


This will change in one of the PRs that is in progress.

Acknowledged. I adjusted the wording to avoid hard dependency on that in-flight PR and kept the note generic.

david-cortes-intel · 2026-02-26T07:44:31Z

dev/bazel/README.md

+
+> Note: Not all compilers support all sanitizers. There is currently no
+> `--config=msan` preset. To use MemorySanitizer, use a compiler that supports
+> it (icpx or clang) and pass flags manually:


Some sanitizers also requiring linking with LLD.

Added README note in a5f1714 that MSan/TSan with Clang may require --linkopt=-fuse-ld=lld.

napetrov · 2026-02-26T21:24:29Z

Addressed the feedback:

Added --config=dbg-symbols inside all sanitizer configurations, so debug symbols are now generated automatically alongside sanitizers.
Added --config=msan (MemorySanitizer) and --config=type (Type Sanitizer) presets.
Clarified in README that sanitizers do not automatically enable assertions/unoptimized builds on their own, and should be paired with --config=dbg or --enable_assert=True.
Added documentation for enabling standard library assertions (-D_GLIBCXX_DEBUG) via --copt.

Copilot

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

Copilot · 2026-03-02T20:08:44Z

dev/bazel/README.md

+The `//:release` target automatically compiles all ISA variants when `--cpu`
+is left at its default value (`auto`). If `--cpu` is set explicitly — e.g. in
+a personal `~/.bazelrc` or passed in CI — the transition respects that value.


The README claims //:release “automatically compiles all ISA variants” when --cpu is left at its default (auto). In the current Bazel config, @config//:cpu defaults to auto, which expands to sse2 + the detected host ISA (not all ISAs), and there’s no transition in the repo that forces all for //:release. Please update this section to match the actual behavior (e.g., document --cpu=all for full ISA coverage) or add the missing transition if that’s the intent.

Copilot · 2026-03-02T20:08:45Z

dev/bazel/README.md

+| `OPTFLAG=O2` | `--copt=-O2` | Override optimization level |
+| `COPT=-flag` | `--copt=-flag` | Arbitrary compiler flag |
+| `--cpu=<isa>` (Make `PLAT`) | `--cpu=<isa>` | ISA selection |
+| (Make default all ISAs) | `bazel build //:release` | Transition forces all ISAs |


In the Make→Bazel reference table, the row stating “Transition forces all ISAs” for bazel build //:release doesn’t match the current implementation (no ISA-forcing transition present; default --cpu=auto builds sse2 + host ISA). Please correct the note to avoid misleading users.

Suggested change

| (Make default all ISAs) | `bazel build //:release` | Transition forces all ISAs |

| (Make default all ISAs) | `bazel build //:release` | Default `--cpu=auto` builds `sse2` + host ISA |

Copilot · 2026-03-02T20:08:45Z

dev/bazel/README.md

+> Note: The `libonedal_dpc.so` library does not support debug mode due to
+> excessive debug information causing long link times. Use the static library
+> variant for DPC++ debugging.


The note says libonedal_dpc.so “does not support debug mode”, but the Bazel release target selects :dynamic_dpc based only on release_dpc and does not gate it on dbg/opt. Unless there is an actual build-time restriction elsewhere, this reads as inaccurate. Consider rephrasing to something verifiable (e.g., “debug builds may be impractically slow/large for the DPC++ shared library”) or document the concrete limitation/condition.

Suggested change

> Note: The `libonedal_dpc.so` library does not support debug mode due to

> excessive debug information causing long link times. Use the static library

> variant for DPC++ debugging.

> Note: Debug builds of the `libonedal_dpc.so` shared library may produce

> excessive debug information and result in very long link times. For

> practical DPC++ debugging, it is recommended to use the static library

> variant instead.

Copilot · 2026-03-02T20:08:45Z

.bazelrc

+# The //:release target automatically builds all ISA variants when
+# --cpu is unset (auto). Use --cpu=<isa> to restrict for CI speed.
+#   bazel build //:release                       # CPU only, all ISAs


These comments state that //:release builds “all ISA variants” when --cpu is unset/auto. In the current config, --cpu=auto expands to sse2 + the detected host ISA, not all ISAs. Please update the comment/examples to match reality (or switch examples to --cpu=all if the intent is full ISA coverage).

Suggested change

# The //:release target automatically builds all ISA variants when

# --cpu is unset (auto). Use --cpu=<isa> to restrict for CI speed.

# bazel build //:release # CPU only, all ISAs

# By default, the //:release target builds for SSE2 plus the detected host

# ISA when --cpu is unset (auto). Use --cpu=all for all ISAs, or

# --cpu=<isa> to restrict for CI speed.

# bazel build //:release # CPU only, SSE2 + host ISA

# bazel build //:release --cpu=all # CPU only, all ISAs

Copilot · 2026-03-02T20:08:45Z

.bazelrc

+#   bazel build //:release --config=release-dpc  # with DPC++ libs
+#   bazel build //:release --cpu=avx2            # CI: avx2 only
+build:release-dpc \
+    --release_dpc=true


--release_dpc=true uses a different boolean spelling/casing than the other config flags in this repo (e.g., config settings compare against "True"). For consistency (and to avoid any ambiguity in bool parsing), use True/False here as well.

Suggested change

--release_dpc=true

--release_dpc=True

Copilot · 2026-03-02T20:08:46Z

.bazelrc

+# Fast local development build — compiles only for the host machine's
+# highest ISA (auto-detected). Use this to speed up iterative builds.
+# NOT suitable for release/packaging.


The dev config description says it “compiles only for the host machine's highest ISA”, but --cpu=auto still includes the sse2 baseline in addition to the detected host ISA (per cpu_info implementation). Please adjust the wording so developers aren’t surprised by the extra ISA being built.

Suggested change

# Fast local development build — compiles only for the host machine's

# highest ISA (auto-detected). Use this to speed up iterative builds.

# NOT suitable for release/packaging.

# Fast local development build — compiles for the host machine's

# highest ISA (auto-detected), plus the baseline sse2 variant. Use this

# to speed up iterative builds. NOT suitable for release/packaging.

BLOCKER 5: Build options parity with Make (REQDBG / REQSAN) - .bazelrc: --config=dbg (REQDBG=1: debug symbols + assertions) - .bazelrc: --config=dbg-symbols (REQDBG=symbols: debug symbols only) - .bazelrc: --config=asan, --config=asan-static (REQSAN=address/static) - .bazelrc: --config=tsan (REQSAN=thread) - .bazelrc: --config=ubsan (REQSAN=undefined) - Custom flags via --copt/--linkopt documented (equiv. to Make COPT/CXXFLAGS) BLOCKER 6: Bazel build documentation - dev/bazel/README.md: Debug and sanitizer builds section - dev/bazel/README.md: Release build section - dev/bazel/README.md: Custom compiler/linker flags section - dev/bazel/README.md: Make to Bazel flag reference table Part of uxlfoundation#3530.

- .bazelrc: dbg-symbols uses --copt=-g instead of --compilation_mode=dbg (avoids unwanted assertions and -O0 from dbg toolchain feature) - .bazelrc: asan drops -shared-libasan (breaks GCC; compiler defaults correctly) - .bazelrc: all debug/sanitizer configs use common: instead of build: so they apply uniformly to both 'bazel build' and 'bazel test' - README.md: msan note rephrased in Bazel terms (no Make REQSAN reference) - README.md: ISA transition wording clarified — forces all ISAs only when --cpu is auto (default); explicit --cpu is respected

Per david-cortes-intel review: use --cxxopt for C++-only flags (e.g. -D_GLIBCXX_DEBUG), --copt for flags that apply to both C and C++. Updated Standard Library Assertions section and Custom Flags section.

Copilot

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

Copilot · 2026-03-07T04:32:21Z

.bazelrc

+# The //:release target automatically builds all ISA variants when
+# --cpu is unset (auto). Use --cpu=<isa> to restrict for CI speed.
+#   bazel build //:release                       # CPU only, all ISAs
+#   bazel build //:release --config=release-dpc  # with DPC++ libs
+#   bazel build //:release --cpu=avx2            # CI: avx2 only


The comments here say //:release builds all ISA variants when --cpu is left at the default (auto). In the current config system, @config//:cpu defaults to auto, which resolves to a single auto-detected ISA (not all). Consider updating the comment/examples to use --cpu=all (or --cpu=modern / an explicit list) for “all ISA variants” behavior, and reserve auto for single-ISA dev builds.

Suggested change

# The //:release target automatically builds all ISA variants when

# --cpu is unset (auto). Use --cpu=<isa> to restrict for CI speed.

# bazel build //:release # CPU only, all ISAs

# bazel build //:release --config=release-dpc # with DPC++ libs

# bazel build //:release --cpu=avx2 # CI: avx2 only

# The //:release target builds multiple ISA variants when

# --cpu is set to 'all' (or another multi-ISA setting). By default,

# @config//:cpu is 'auto', which selects a single host ISA.

# bazel build //:release --cpu=all # CPU only, all ISAs

# bazel build //:release --config=release-dpc --cpu=all # with DPC++ libs

# bazel build //:release --cpu=avx2 # CI: avx2 only

Copilot · 2026-03-07T04:32:22Z

.bazelrc

+common:dbg \
+    --compilation_mode=dbg \
+    --enable_assert=True
+
+# Configuration: 'dbg-symbols'
+# Debug symbols only — no assertion checking, no -O0.
+# Equivalent to Make: REQDBG=symbols
+# Adds -g to the default opt build; preserves -O2/-O3 optimization.
+#   bazel build //:release --config=dbg-symbols
+common:dbg-symbols \
+    --copt=-g \
+    --cxxopt=-g


Using common:<config> means these options will also be applied to non-build commands when invoked with --config=... (e.g., bazel query), which can cause “unknown option” failures for flags like --compilation_mode, --copt, and --linkopt. To keep configs usable across Bazel subcommands, consider defining these as build:<config> and test:<config> (duplicated), rather than common:<config>.

Suggested change

common:dbg \

--compilation_mode=dbg \

--enable_assert=True

# Configuration: 'dbg-symbols'

# Debug symbols only — no assertion checking, no -O0.

# Equivalent to Make: REQDBG=symbols

# Adds -g to the default opt build; preserves -O2/-O3 optimization.

# bazel build //:release --config=dbg-symbols

common:dbg-symbols \

--copt=-g \

--cxxopt=-g

build:dbg \

--compilation_mode=dbg \

--enable_assert=True

test:dbg \

--compilation_mode=dbg \

--enable_assert=True

# Configuration: 'dbg-symbols'

# Debug symbols only — no assertion checking, no -O0.

# Equivalent to Make: REQDBG=symbols

# Adds -g to the default opt build; preserves -O2/-O3 optimization.

# bazel build //:release --config=dbg-symbols

build:dbg-symbols \

--copt=-g \

--cxxopt=-g

test:dbg-symbols \

--copt=-g \

--cxxopt=-g

Copilot · 2026-03-07T04:32:22Z

.bazelrc

+
+# Configuration: 'type'
+# Type sanitizer build.
+common:type \
+    --copt=-fsanitize=type \
+    --copt=-fno-omit-frame-pointer \
+    --linkopt=-fsanitize=type \


--config=type uses -fsanitize=type, which is Clang-only (GCC doesn’t support TypeSanitizer). Consider documenting that this config requires Clang/ICPX (similar to the MSan note), so users on GCC don’t get a confusing compiler error.

Copilot · 2026-03-07T04:32:22Z

dev/bazel/README.md

+---
+
+## Release Build
+
+Build the full release artifact (all ISA variants: sse2, sse42, avx2, avx512):
+
+```sh
+bazel build //:release
+```
+
+The `//:release` target automatically compiles all ISA variants when `--cpu`


This section says bazel build //:release builds “all ISA variants” and that the default --cpu=auto triggers that. In the current Bazel config, @config//:cpu defaults to auto, which selects a single auto-detected ISA. Please update the instructions to use --cpu=all (or modern / explicit ISA list) when you mean “all ISA variants”, and clarify what auto does.

Copilot · 2026-03-07T04:32:22Z

dev/bazel/README.md

+| `OPTFLAG=O2` | `--copt=-O2` | Override optimization level |
+| `COPT=-flag` | `--copt=-flag` (C+C++) / `--cxxopt=-flag` (C++ only) | Arbitrary compiler flag |
+| `--cpu=<isa>` (Make `PLAT`) | `--cpu=<isa>` | ISA selection |
+| (Make default all ISAs) | `bazel build //:release` | Transition forces all ISAs |


The “Make default all ISAs” mapping here assumes bazel build //:release forces all ISA builds, but the current --cpu default (auto) is single-ISA. Update this table row to reflect the actual flag needed for all-ISA coverage (e.g., --cpu=all).

Suggested change

| (Make default all ISAs) | `bazel build //:release` | Transition forces all ISAs |

| (Make default all ISAs) | `bazel build //:release --cpu=all` | Transition forces all ISAs |

Copilot · 2026-03-07T04:32:22Z

dev/bazel/README.md

+```
+
+### Type Sanitizer
+


The Type Sanitizer section doesn’t mention compiler requirements. -fsanitize=type is Clang-only; GCC users will see a hard failure. Consider adding a short note (like the MSan section) indicating this requires Clang/ICPX and may be unavailable depending on the toolchain.

Suggested change

Requires Clang or ICPX. GCC does not support the Type Sanitizer and availability may depend on your toolchain.

Copilot AI review requested due to automatic review settings February 25, 2026 00:24

napetrov requested review from Alexandr-Solovev, avolkov-intel, david-cortes-intel, ethanglaser and icfaust as code owners February 25, 2026 00:24

Copilot started reviewing on behalf of napetrov February 25, 2026 00:24 View session

napetrov mentioned this pull request Feb 25, 2026

[Bazel Migration] Master Tracking Issue (Make parity) #3530

Open

napetrov added documentation infra labels Feb 25, 2026

Copilot AI reviewed Feb 25, 2026

View reviewed changes

napetrov marked this pull request as draft February 25, 2026 03:27

napetrov force-pushed the bazel-debug-sanitizer-docs branch from 1cecb48 to 92dc524 Compare February 25, 2026 03:30

david-cortes-intel reviewed Feb 26, 2026

View reviewed changes

napetrov added the bazel label Feb 26, 2026

napetrov marked this pull request as ready for review March 2, 2026 20:03

Copilot AI review requested due to automatic review settings March 2, 2026 20:03

Copilot started reviewing on behalf of napetrov March 2, 2026 20:03 View session

Copilot AI reviewed Mar 2, 2026

View reviewed changes

napetrov added 3 commits March 5, 2026 10:09

bazel: address PR feedback on sanitizers and debug docs

9fa277e

napetrov force-pushed the bazel-debug-sanitizer-docs branch from 86d3d4b to 9fa277e Compare March 5, 2026 18:09

napetrov mentioned this pull request Mar 7, 2026

bazel: add release structure improvements (versioning, SONAME, vars.sh, pkg-config) #3513

Open

docs(bazel): clarify --copt vs --cxxopt usage in README

04b6db8

Per david-cortes-intel review: use --cxxopt for C++-only flags (e.g. -D_GLIBCXX_DEBUG), --copt for flags that apply to both C and C++. Updated Standard Library Assertions section and Custom Flags section.

Copilot AI review requested due to automatic review settings March 7, 2026 04:27

Copilot started reviewing on behalf of napetrov March 7, 2026 04:27 View session

bazel: improve MSan guidance (track-origins + optional lld note)

a5f1714

Copilot AI reviewed Mar 7, 2026

View reviewed changes

		> Note: Not all compilers support all sanitizers. GCC will fail with
		> `REQSAN=memory` by design. Use icpx or clang for memory sanitizer.

-> Note: Not all compilers support all sanitizers. GCC will fail with
-> `REQSAN=memory` by design. Use icpx or clang for memory sanitizer.
+> Note: Not all compilers support all sanitizers. In the Make-based flow,
+> MemorySanitizer corresponds to `REQSAN=memory`, but there is currently no
+> Bazel `--config` preset for msan. To use MemorySanitizer with Bazel you must
+> use a compiler that supports it (such as icpx or clang) and pass the
+> appropriate flags (for example, `--copt=-fsanitize=memory` and related msan
+> options). GCC does not support MemorySanitizer and will fail by design.

		The `//:release` target automatically compiles all ISA variants regardless of
		the `--cpu` flag default. To restrict ISA coverage (e.g., for faster CI):

	--linkopt=-fsanitize=address \
	--linkopt=-shared-libasan
	--linkopt=-fsanitize=address


		## Custom Compiler and Linker Flags

		Equivalent to Make `COPT` / `CXXFLAGS`. Pass via `--copt` and `--linkopt`:

	\| (Make default all ISAs) \| `bazel build //:release` \| Transition forces all ISAs \|
	\| (Make default all ISAs) \| `bazel build //:release` \| Default `--cpu=auto` builds `sse2` + host ISA \|

-> Note: The `libonedal_dpc.so` library does not support debug mode due to
-> excessive debug information causing long link times. Use the static library
-> variant for DPC++ debugging.
+> Note: Debug builds of the `libonedal_dpc.so` shared library may produce
+> excessive debug information and result in very long link times. For
+> practical DPC++ debugging, it is recommended to use the static library
+> variant instead.

-# The //:release target automatically builds all ISA variants when
-# --cpu is unset (auto). Use --cpu=<isa> to restrict for CI speed.
-#   bazel build //:release                       # CPU only, all ISAs
+# By default, the //:release target builds for SSE2 plus the detected host
+# ISA when --cpu is unset (auto). Use --cpu=all for all ISAs, or
+# --cpu=<isa> to restrict for CI speed.
+#   bazel build //:release                       # CPU only, SSE2 + host ISA
+#   bazel build //:release --cpu=all             # CPU only, all ISAs



	Requires Clang or ICPX. GCC does not support the Type Sanitizer and availability may depend on your toolchain.

Conversation

napetrov commented Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

BLOCKER 5: Build options parity with Make

BLOCKER 6: Build documentation

Changes

Testing

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

napetrov commented Feb 25, 2026

Uh oh!

david-cortes-intel commented Feb 25, 2026

Uh oh!

napetrov commented Feb 25, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

napetrov commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 2, 2026

Choose a reason for hiding this comment

napetrov commented Feb 25, 2026 •

edited

Loading

napetrov commented Feb 26, 2026 •

edited

Loading