Skip to content

rvalue() - #1721

Draft
alejandro-colomar wants to merge 4 commits into
shadow-maint:masterfrom
alejandro-colomar:rvalue
Draft

rvalue()#1721
alejandro-colomar wants to merge 4 commits into
shadow-maint:masterfrom
alejandro-colomar:rvalue

Conversation

@alejandro-colomar

Copy link
Copy Markdown
Collaborator

Compound literals are lvalues, and thus somewhat dangerous.  Their
address can be taken, and they can be assigned to.

We were using statement expressions to perform lvalue conversion
on compound literals, transforming them to rvalues, and thus removing
their dangers.  However, statement expressions are non-standard, and
quite complex within the compiler, so it would be interesting to use
simpler compiler features to achieve the same.

The comma operator also performs lvalue conversion, and we can use
a dummy (void)0 expression to introduce it.  This is significantly
simpler, and is more portable than the statement expression: it is valid
all the way back to C99 (the comma operator and the (void)0 expression
are portable to C89, but the compound literal is from C99).

By using a simpler feature, we have a smaller risk of running into
a compiler bug.

Suggested-by: Martin Uecker <uecker@tugraz.at>
Cc: Christopher Bazley <chris.bazley@arm.com>
Cc: Kees Cook <kees@kernel.org>
Cc: Richard Russon <rich@flatcap.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
This macro takes an lvalue, and performs lvalue conversion, resulting in
an rvalue.

Signed-off-by: Alejandro Colomar <alx@kernel.org>
This helps document why we use '(void)0' with the comma operator.

Signed-off-by: Alejandro Colomar <alx@kernel.org>
These macros already perform lvalue conversion thanks to the comma
operator used for the _Generic() expressions.  However, we may forget
about that if we ever remove those _Generic() expressions for some
reason, so let's make sure that we perform lvalue conversion on those
compound literals regardless of that.

Signed-off-by: Alejandro Colomar <alx@kernel.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant