Skip to content

LangRef: storing poison in memory is UB #141339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
+6 −0
Closed

LangRef: storing poison in memory is UB #141339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions llvm/docs/LangRef.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11433,6 +11433,12 @@ If ``<value>`` is of aggregate type, padding is filled with
:ref:`undef <undefvalues>`.
If ``<pointer>`` is not a well-defined value, the behavior is undefined.

If ``<value>`` is poison, then behavior currently is effectively undefined due
to the fact that many LLVM passes assume they can do load widening, and having
poison in memory would "infect" the entire widened load. This can hopefully be
alleviated in the future, but until then, frontends should refrain from
generating code that stores poison values in memory.

Example:
""""""""

Expand Down
Loading