Skip to content

Reasoning for and potential side effects of linking cudart_static? #735

@BwL1289

Description

@BwL1289

As discussed here, implemented here, and documented here, my team and I are wondering what the reasoning was behind linking unconditionally linking cudart_static in setup.py in the newest version of cuda_bindings?

We've read through the full conversation and are still unclear why it's needed.

Potentially more importantly, could there be any unintended side effects as cuda_bindings may also load libcudart dynamically at runtime?

The reason for asking is due to trying to keep the same cuda libraries consistently linked statically or dynamically across all libraries (for example, torch mixes linking static and dynamic cuda libraries and we want to ensure we're always linking the cuda libraries the same way).

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageNeeds the team's attention

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions