Skip to content

cuda.core: LinkerOptions passes true/false to nvJitLink backend, which only accepts 0/1 #3254

Closed

Description

@lijinf2

LinkerOptions._prepare_nvjitlink_options() passes Python-style true/false
(and raw "True"/"False" for -split-compile / -split-compile-extended)
to the nvJitLink backend for boolean options (-ftz, -prec-div,
-prec-sqrt, -fma, -split-compile, -split-compile-extended).

nvJitLink only accepts 0/1 for these options. It silently ignores the
invalid true/false values, so the option appears to be set successfully
but causes incorrect behavior / errors at runtime.

Reported in nvbug 6621758. Fix in #3128.

Activity

  1. self-assigned this
    on Oct 27, 2026
  2. added this to the cuda.core 1.3.0 milestone on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

triageNeeds the team's attention

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions