Christian Blichmann 5c7903ecd9 Check for either violate() or ViolateIndirect() in stack trace ... Depending on architecture and optimization level, the compiler may choose to not generate full stack frames, even with no-inline and no tail-call attributes. PiperOrigin-RevId: 372339987 Change-Id: I42043131bbb6092ff234e80ae9047f7a2bf31161		2021-05-06 07:36:13 -07:00
..
hello_sapi	Build fixes for recent Bazel versions	2020-09-25 07:25:31 -07:00
stringop	Check for either violate() or ViolateIndirect() in stack trace	2021-05-06 07:36:13 -07:00
sum	Replace usage of deprecated functions within Sandboxed API	2021-03-18 05:39:50 -07:00
zlib	Prefixed (unique) names for executables in cmake	2020-12-14 01:13:31 -08:00
CMakeLists.txt	Enable shared libraries build and cross-compilation	2020-12-14 09:16:14 -08:00