mirror of
https://github.com/RPCS3/llvm.git
synced 2024-12-28 23:43:50 +00:00
whitespace
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@187437 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
d71efffdcf
commit
c0c9205811
@ -59,7 +59,7 @@ namespace llvm {
|
||||
// poisoned, so that dangling SlotIndex access can be reliably detected.
|
||||
void setPoison() {
|
||||
intptr_t tmp = reinterpret_cast<intptr_t>(mi);
|
||||
assert(((tmp & 0x1) == 0x0) && "Pointer already poisoned?");
|
||||
assert(((tmp & 0x1) == 0x0) && "Pointer already poisoned?");
|
||||
tmp |= 0x1;
|
||||
mi = reinterpret_cast<MachineInstr*>(tmp);
|
||||
}
|
||||
@ -672,7 +672,7 @@ namespace llvm {
|
||||
/// performance. Any remaining SlotIndex objects that point to the same
|
||||
/// index are left 'dangling' (much the same as a dangling pointer to a
|
||||
/// freed object) and should not be accessed, except to destruct them.
|
||||
///
|
||||
///
|
||||
/// Like dangling pointers, access to dangling SlotIndexes can cause
|
||||
/// painful-to-track-down bugs, especially if the memory for the index
|
||||
/// previously pointed to has been re-used. To detect dangling SlotIndex
|
||||
|
Loading…
Reference in New Issue
Block a user