ORNL / ORNL/GridKit

Build issue: Unable to build with undefined behavior sanitizer and Enzyme

Open
#141 0 comments 0 reactions 1 assignee View on GitHub

@nkoukpaizan is already working on this.

Since Jun 13, 2025.

automatic differentiation cmake development
Dominant language
C++
Stars
27
Forks
11
Avg merge
3d 8h
Merged PRs (30d)
23

Description

Build error message(s)

Build error when -DGRIDKIT_ENABLE_UBSAN=On and -DGRIDKIT_ENABLE_ENZYME=On.

[  6%] Building CXX object src/Model/PhasorDynamics/Load/CMakeFiles/phasor_dynamics_load_obj_shared.dir/LoadEnzyme.cpp.o
error: Enzyme: No forward mode derivative found for __ubsan_handle_type_mismatch_v1
 at context:   tail call void @__ubsan_handle_type_mismatch_v1(ptr nonnull @1074, i64 %5) #24, !nosanitize !7
error: Enzyme: No forward mode derivative found for __ubsan_handle_dynamic_type_cache_miss
 at context:   tail call void @__ubsan_handle_dynamic_type_cache_miss(ptr nonnull @1075, i64 %5, i64 %16) #24, !nosanitize !8
error: Enzyme: No forward mode derivative found for __ubsan_handle_type_mismatch_v1
 at context:   tail call void @__ubsan_handle_type_mismatch_v1(ptr nonnull @130, i64 %214) #24, !nosanitize !18
error: Enzyme: No forward mode derivative found for __ubsan_handle_pointer_overflow
 at context:   tail call void @__ubsan_handle_pointer_overflow(ptr nonnull @131, i64 %214, i64 %222) #24, !nosanitize !19
error: Enzyme: No forward mode derivative found for __ubsan_handle_type_mismatch_v1
 at context:   tail call void @__ubsan_handle_type_mismatch_v1(ptr nonnull @132, i64 %226) #24, !nosanitize !20

cc @pelesh @wmoses

GridKit™ version

9b92afb99d2ee135416e9c0058d67590c21ef7e6

System and environment details

Tested on Frontier

  • linux-sles15-zen3
  • Enzyme 0.0.173 built with Spack
  • LLVM 19.1.7 built with Spack
Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.