llnl / llnl/RAJAPerf

please add compiler flags to suppress annoying warnings during Release builds

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

@rhornung67 is already working on this.

Since Jan 19, 2023.

build enhancement
Dominant language
Jupyter Notebook
Stars
135
Forks
55
Avg merge
4d 16h
Merged PRs (30d)
5

Description

This is a feature request. I'm not optimistic you'll accept it. At worst, this will be documentation for future users who want this.

Warnings are very good for developers, and in Debug builds. I'm not sure they help in Release builds, since they can cause unnecessary concern by users (at least the demented ones who actually look at compiler warnings).

This warning is annoying:

 line 38: warning: a volatile operand to an increment expression is deprecated
        for (RepIndex_type irep = 0; irep < run_reps; ++irep) {
                                                        ^

Every compiler has a way to suppress it.

The other annoying warning that appears all over the place is related to unused parameters.

Compiler Volatile Flag Unused Flag
GCC -Wno-volatile -Wno-unused-parameter
Clang -Wno-deprecated-volatile -Wno-unused-parameter
Intel NextGen -Wno-deprecated-volatile -Wno-unused-parameter
Intel Classic -diag-disable=4128 -Wno-unused-parameter
NVC++ --diag_supress=volatile_inc_dec_deprecated Unnecessary

The Intel Classic noise suppression device can be used for the following as well, if desired:

remark #11074: Inlining inhibited by limit max-total-size
remark #11076: To get full report use -qopt-report=4 -qopt-report-phase ipo
warning #15552: loop was not vectorized with "simd"
warning #3948: simd pragma has been deprecated, and will be removed in a future release.  Please refer to release notes for details and recommended alternatives
warning #4128: a volatile operand to an increment expression is deprecated
warning #4130: a volatile destination type for a compound assignment expression is deprecated

Contributor guide

No contributing guide indexed for this repository

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.