Title
assert macro is overconstrained
Status
nad
Section
[assertions]
Submitter
David Krauss

Created on 2014-06-25.00:00:00 last changed 9 months ago

Messages

Date: 2023-06-15.00:00:00

[ 2023-06-13, Varna; Status changed: New → NAD. ]

Only observable by stringifying an assert expression anyway, so arguably allowed by implementations anyway. Needs a paper to make changes here, or incorporate into P2884.

Date: 2014-06-25.00:00:00

When NDEBUG is defined, assert must expand exactly to the token sequence ((void)0), with no whitespace (C99 §7.2/1 and also C11 §7.2/1). This is a lost opportunity to pass the condition along to the optimizer.

The user may observe the token sequence using the stringize operator or discriminate it by making a matching #define directive. There is little chance of practical code doing such things. It's reasonable to allow any expansion that is a void expression with no side effects or semantic requirements, for example, an extension keyword or an attribute-specifier finagled into the context.

Conforming optimizations would still be limited to treating the condition as hint, not a requirement. Nonconformance on this point is quite reasonable though, given user preferences. Anyway, it shouldn't depend on preprocessor quirks.

As for current practice, Darwin OS <assert.h> provides a GCC-style compiler hint __builtin_expect but only in debug mode. Shouldn't release mode preserve hints?

Daniel:

The corresponding resolution should take care not to conflict with the intention behind LWG 2234.

History
Date User Action Args
2023-06-13 14:40:28adminsetmessages: + msg13626
2023-06-13 14:40:28adminsetstatus: new -> nad
2014-06-25 00:00:00admincreate