Age | Commit message (Collapse) | Author |
|
It may happen that some older instance of klee is already present
in PATH. All tests that call plain klee instead of %klee may use
it and then unexpectedly fail.
This commit will make all tests that rely on klee tools being
explicitly in PATH fail in our CI. From now on, only LLVM tools,
FileCheck and not will be in lit's PATH.
|
|
CMake 3.19+ started to issue warnings if this policy is set to OLD:
CMake Deprecation Warning at test/CMakeLists.txt:143 (cmake_policy):
The OLD behavior for policy CMP0026 will be removed from a future version
of CMake.
The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
|
|
`make uninstall` is enabled.
Without this, uninstalling was done manually with `rm` command.
|
|
|
|
|
|
Fixes:
CMake Warning (dev) at CMakeLists.txt:478 (set):
implicitly converting 'String' to 'STRING' type.
This warning is for project developers. Use -Wno-dev to suppress it.
|
|
|
|
commit 8ed005daf0ab of glibc-2.33 (Remove stat wrapper functions, move
them to exported symbols) removed renames of `__fxstat`, `__xstat`, and
`__lxstat` to `__fxstat64`, `__xstat64`, and `__lxstat64`, respectively.
But we relied on the renames to build `fd_64.c` properly. With glibc
2.33, we now see link failures of the POSIX runtime:
error: Linking globals named '__xstat': symbol multiply defined!
Rename the functions using `__REDIRECT_NTH` in the code as
`__USE_FILE_OFFSET64` case (which we define at the top of the file by
`#define _FILE_OFFSET_BITS 64`) did exactly that.
Fixes #1384.
|
|
__cxa_throw and __cxa_rethrow were not handled by special function handlers in
the final version of #966 (which introduced support for C++ exception handling)
|
|
otherwise, it is hard to tell whether EH support is available or not
|
|
restoring old behavior without EH support
|
|
|
|
* failing malloc was not handled before, now returns null/ENOMEM
* when path is non-null and size is zero return null/EINVAL
|
|
|
|
|
|
|
|
|
|
|
|
- `-DNDebug` -> `-DNDEBUG`
- different flags for `Release{+Debug,}+Asserts`
- `-g` is no longer part of common flags
- `-D_DEBUG` is now only set for debug builds
- removed unused `LIB_BC_FLAGS_{32,64}`
- added example, architecture prefix for specific flags
|
|
|
|
|
|
|
|
|
|
Automatically detect if 32bit bitcode files can be built.
In this case, build runtime library with 32bit as well.
|
|
|
|
and should be replaced with CallBase::getParamAlign
|
|
See: https://reviews.llvm.org/D80368
|
|
See: https://reviews.llvm.org/D84447
|
|
See:
https://reviews.llvm.org/D75660
https://reviews.llvm.org/D75661
|
|
CallBase::getCalledValue has been deprecated by getCalledOperand since LLVM 8
and has been removed in LLVM 11
See: https://reviews.llvm.org/D78882
|
|
The same applies to SmallString.
See: llvm/llvm-project@777180a#diff-497ba4c0c527a125d382b51a34f32542
|
|
f[k], with k symbolic and f a 4-element vector into something along the lines:
if k == 0 => f[0]
elif k == 1 => f[1]
elif k == 2 => f[2]
elif k == 3 => f[3]
else ==> undef
|
|
f[k] = v, with f a 4-element vector, into something along the lines:
if k == 0 => f[0] = v
if k == 1 => f[1] = v
if k == 2 => f[2] = v
if k == 3 => f[3] = v
|
|
the overflow behaviour is different in LLVM 11.
|
|
|
|
|
|
`sudo` invocation in Github Actions does not provide environment variables,
therefore Codecov was not aware of the correct settings.
This behaviour is different under Github Actions than Travis CI.
This could be fixed via `sudo -E`.
Anyway, tests do not need to be run `sudo` with Github Actions,
so remove the `sudo` invocation in the first place.
|
|
|
|
|
|
Update container build script to utilize Github Actions job description
instead of Travis CI's.
|
|
Add support for Github Actions to use as new CI.
This builds all the components as the original Travis CI script.
|
|
System header files on macOS are not part of `/usr/include` since
Catalina. Instead, multiple locations are possible and depend on the
selected SDK.
Use `xcrun` to automatically detect the correct path on macOS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|