RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-11-30 23:21:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

[docs] Fix a couple spelling errors.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@352439 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Eli Friedman 2019-01-28 23:03:41 +00:00
parent e5aed2f2a4
commit 9276ecc42a
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/LangRef.rst
View File

@ -2184,7 +2184,7 @@ operations relative to non-volatile operations. This is not Java's
A volatile load or store may have additional target-specific semantics.
Any volatile operation can have side effects, and any volatile operation
can read and/or modify state which is not accessible via a regular load
or store in this module. Volatile operations may use adresses which do
or store in this module. Volatile operations may use addresses which do
not point to memory (like MMIO registers). This means the compiler may
not use a volatile operation to prove a non-volatile access to that
address has defined behavior.

2
docs/SpeculativeLoadHardening.md
View File

@ -255,7 +255,7 @@ if (untrusted_size_from_caller < sizeof(local_buffer)) {
memcpy(local_buffer, untrusted_data_from_caller,
untrusted_size_from_caller);
// The stack has now been smashed, writing an attacker-controlled
// address over the return adress.
// address over the return address.
minor_processing(local_buffer);
return;
// Control will speculate to the attacker-written address.