Displaying 10 results from an estimated 10 matches for "with_assert".
Did you mean:
with_asserts
2016 Nov 16
4
[RFC] Runtime checks for ABI breaking build of LLVM
...for many of us and users of LLVM is that an assert build isn’t ABI compatible with a release build.
The CMake flags that controls this behavior is LLVM_ABI_BREAKING_CHECKS (
LLVM_ABI_BREAKING_CHECKS:STRING
Used to decide if LLVM should be built with ABI breaking checks or not. Allowed values are WITH_ASSERTS (default), FORCE_ON and FORCE_OFF. WITH_ASSERTS turns on ABI breaking checks in an assertion enabled build. FORCE_ON (FORCE_OFF) turns them on (off) irrespective of whether normal (NDEBUG-based) assertions are enabled or not. A version of LLVM built with ABI breaking checks is not ABI compatible...
2016 Nov 16
2
[RFC] Runtime checks for ABI breaking build of LLVM
...ible with a release build.
>>
>> The CMake flags that controls this behavior is LLVM_ABI_BREAKING_CHECKS (
>>
>> *LLVM_ABI_BREAKING_CHECKS*:STRING
>> Used to decide if LLVM should be built with ABI breaking checks or
>> not. Allowed values
>> are WITH_ASSERTS (default), FORCE_ON and FORCE_OFF. WITH_ASSERTS turns
>> on ABI breaking checks in an assertion enabled
>> build. FORCE_ON (FORCE_OFF) turns them on (off) irrespective of
>> whether normal (NDEBUG-based) assertions are enabled or not. A
>> version of LLVM buil...
2016 Dec 14
2
Non-determinism in LLVM codegen
...nalysis/malloc.c
> Clang :: Rewriter/objc-modern-metadata-visibility.mm
> Clang :: SemaCXX/warn-loop-analysis.cpp
> LLVM :: Transforms/SimplifyCFG/bug-25299.ll
Wait, so you committed a patch that breaks these tests? Should you fix
them first?
IIUC, LLVM_ABI_BREAKING_CHECKS is WITH_ASSERTS by default, so your
change, which is known to break things, is enabled for those of us
enabling asserts?
Or am I misunderstanding?
2016 Dec 14
0
Non-determinism in LLVM codegen
...:: Rewriter/objc-modern-metadata-visibility.mm
>> Clang :: SemaCXX/warn-loop-analysis.cpp
>> LLVM :: Transforms/SimplifyCFG/bug-25299.ll
>
> Wait, so you committed a patch that breaks these tests? Should you fix
> them first?
>
> IIUC, LLVM_ABI_BREAKING_CHECKS is WITH_ASSERTS by default, so your
> change, which is known to break things, is enabled for those of us
> enabling asserts?
>
> Or am I misunderstanding?
Looks like Mehdi reverted already.
2019 Jan 08
4
[LLD] [WASM] wasm/function-index.test failing
I cannot reproduce this error, but this could be real.
David, is this reproducible every time or is this flaky?
On Mon, Jan 7, 2019 at 5:03 PM Heejin Ahn via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello David,
>
> I use x86_64 and it works on my machine. I also can't find this error on
> LLVM buildbot page. I'd appreciate if you help me reproduce the problem.
2016 Dec 14
0
Non-determinism in LLVM codegen
Everyone,
The following patch to reverse iterate SmallPtrSet's has now been merged:
https://reviews.llvm.org/D26718
This is how LLVM behavior will change due to this patch:
- In LLVM builds with *assertions enabled*, SmallPtrSet's would always
be reverse iterated by default.
This default behavior can be overridden via the flag "-mllvm
-reverse-iterate=<true/false>".
2016 Mar 17
2
Building with LLVM_PARALLEL_XXX_JOBS
On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote:
[ brutal-snip ]
...
> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more
> optimized binaries) ]
>
> How do I anable LTO via CMAKE?
>
>
> LLVM_ENALBLE_LTO=On
>
[ v4 of my build-script attached ]
Hi Chris,
thanks for the response!
That seems to work (see below).
$ cd
2016 Nov 15
9
Non-determinism in LLVM codegen
Everyone,
There is non-determinism in LLVM codegen in the following scenarios:
1. Between back-to-back runs of the same LLVM toolchain
2. Between Release vs Release+Asserts toolchains
3. Between Linux vs Windows toolchains
The main reasons for the non-determinism in codegen are:
1. Iteration of unordered containers (like SmallPtrSet, DenseMap, etc)
where the iteration order is undefined
2.
2017 Feb 11
2
Asan self host problems: Failed to deallocate
Trying to run a self host "ninja check-clang" with ASan enabled I hit a
/lot/ of errors like this (strangely I hit none of these in check-llvm,
only in check-clang):
Any ideas?
==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes
at address 0x631000014800
==10525==AddressSanitizer CHECK failed:
2017 Feb 15
2
Asan self host problems: Failed to deallocate
...PENDS:STATIC=
//Dependencies for target
LLVMXCoreDesc_LIB_DEPENDS:STATIC=
//Dependencies for target
LLVMXCoreDisassembler_LIB_DEPENDS:STATIC=
//Dependencies for target
LLVMXCoreInfo_LIB_DEPENDS:STATIC=
//Dependencies for target
LLVMXRay_LIB_DEPENDS:STATIC=
//Enable abi-breaking checks. Can be WITH_ASSERTS, FORCE_ON or
// FORCE_OFF.
LLVM_ABI_BREAKING_CHECKS:STRING=WITH_ASSERTS
//Append the version control system revision id to LLVM version
LLVM_APPEND_VC_REV:BOOL=OFF
//Value Computed by CMake
LLVM_BINARY_DIR:STATIC=/usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalon...