You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature_single_flag_c_cpp macro defaults each feature to enabled.
While these warnings are relevant to the OpenTitan codebase, they are overly-strict for some codebases. I'd prefer to see some of these features disabled by default and explicitly enabled in a project's .bazelrc file with additional --features=... switches.
We should also consider whether we should group these warnings into classes (ie: low, medium, high) and allow enable/disable of each class of warning feature with a single --features=... switch.
The text was updated successfully, but these errors were encountered:
There are a number of feature flags related to compiler warnings:
https://github.com/lowRISC/crt/blob/main/features/common/BUILD.bazel#L45-L113
https://github.com/lowRISC/crt/blob/main/features/embedded/BUILD.bazel#L91-L104
The
feature_single_flag_c_cpp
macro defaults each feature to enabled.While these warnings are relevant to the OpenTitan codebase, they are overly-strict for some codebases. I'd prefer to see some of these features disabled by default and explicitly enabled in a project's
.bazelrc
file with additional--features=...
switches.We should also consider whether we should group these warnings into classes (ie:
low
,medium
,high
) and allow enable/disable of each class of warning feature with a single--features=...
switch.The text was updated successfully, but these errors were encountered: