forked from OSchip/llvm-project
parent
146307eb52
commit
4e442d75e5
|
@ -29,7 +29,7 @@ can model and optimize such code.
|
|||
|
||||
If the accesses are not aligned with the size of the access type we model them
|
||||
as multiple accesses to an array of smaller elements. This is especially
|
||||
usefull for structs containing different typed elements as accesses to them are
|
||||
useful for structs containing different typed elements as accesses to them are
|
||||
represented using only one base pointer, namely the ``struct`` itself. In the
|
||||
example below the accesses to ``s`` are all modeled as if ``s`` was a single
|
||||
char array because the accesses to ``s->A`` and ``s->B`` are not aligned with
|
||||
|
@ -60,8 +60,8 @@ supported before, we now allow and model two other kinds. The first are
|
|||
intrinsic calls to ``memcpy``, ``memmove`` and ``memset``. These calls can be
|
||||
represented precisely if the pointers involved are known and the given length
|
||||
is affine. Additionally, we allow to over-approximate function calls that are
|
||||
known only to read memory, read memory accesible through pointer arguments or
|
||||
access only memory accesible through pointer arguments. See also the function
|
||||
known only to read memory, read memory accessible through pointer arguments or
|
||||
access only memory accessible through pointer arguments. See also the function
|
||||
attributes ``readonly`` and ``argmemonly`` for more information.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue