Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable more warnings as errors in CUDA CI configurations #1154

Open
msimberg opened this issue May 29, 2024 · 0 comments
Open

Enable more warnings as errors in CUDA CI configurations #1154

msimberg opened this issue May 29, 2024 · 0 comments

Comments

@msimberg
Copy link
Collaborator

We currently use -Werror=all-warnings in CI. However, it seems like this doesn't actually enable all warnings. nvcc --help says:

--Werror <kind>,...                             (-Werror)
        Make warnings of the specified kinds into errors.  The following is the list
        of warning kinds accepted by this option:

        cross-execution-space-call
                Be more strict about unsupported cross execution space calls.
                The compiler will generate an error instead of a warning for a
                call from a __host__ __device__ to a __host__ function.
        reorder
                Generate errors when member initializers are reordered.
        deprecated-declarations
                Generate error on use of a deprecated entity.
        default-stream-launch
                Generate error when an explicit stream argument is not provided in
        the <<<...>>> kernel launch syntax.
        missing-launch-bounds
                Generate error when a __global__ function does not have an explicit
        __launch_bounds__ annotation.
        ext-lambda-captures-this
                Generate error when an extended lambda implicitly captures 'this'
        Allowed values for this option:  'all-warnings','cross-execution-space-call',
        'default-stream-launch','deprecated-declarations','ext-lambda-captures-this',
        'missing-launch-bounds','reorder'.

The non-all-warnings errors seem to enable warnings in addition to all-warnings. We should check if these additional warnings are useful to enable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant