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
I'm not sure if the warning is the only observable problem. Classifying the result of the extern function call as a compile-time constant could have a less benign effect somewhere else.
The text was updated successfully, but these errors were encountered:
kfcripps
added
the
core
Topics concerning the core segments of the compiler (frontend, midend, parser)
label
May 10, 2024
…me constants. (#4726)
* Do not mark argument-less extern method calls as compile-time constants.
Signed-off-by: kfcripps <kyle@pensando.io>
* Only mark pure extern function calls with const args as compile-time constants
Signed-off-by: kfcripps <kyle@pensando.io>
* Add tests
Signed-off-by: kfcripps <kyle@pensando.io>
* Fixes for static_assert() and factory extern functions
Signed-off-by: kfcripps <kyle@pensando.io>
* Appease cpplint
Signed-off-by: kfcripps <kyle@pensando.io>
* Do not unconditionally mark results of pure extern method function calls as compile-time constants
Signed-off-by: kfcripps <kyle@pensando.io>
* Also check for IR::Type_SpecializedCanonical with base type of IR::Type_Extern
Signed-off-by: kfcripps <kyle@pensando.io>
---------
Signed-off-by: kfcripps <kyle@pensando.io>
Compiling
results in the following warning:
I'm not sure if the warning is the only observable problem. Classifying the result of the extern function call as a compile-time constant could have a less benign effect somewhere else.
The text was updated successfully, but these errors were encountered: