Displaying 15 results from an estimated 15 matches for "testbodi".
Did you mean:
testbody
2011 Jul 23
2
[LLVMdev] Build of latest llvm gives warning and error
Building of llvm with gcc-4.5.2-1 gives these warnings:
1) Building FileManagerTest
"llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build
C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp:
In member function 'virtual
void<unnamed>::FileManagerTest_NoVirtualDirectoryExistsBeforeAVirtualFileIsAdded_Test::TestBody()':
2014 Jun 30
3
[LLVMdev] LLD dynamic compilation
On 30 June 2014 16:16, Shankar Easwaran <shankare at codeaurora.org> wrote:
> I think you are hitting a bug, the Observer pattern was added a few weeks
> back, and may be there is some sort of uninitialized variable ?
This is my back-trace at "-O2 -g" (since -O1 pass):
operator() (file=<optimized out>, __closure=0x7fffffffde40) at
2015 Dec 15
2
Trouble supressing ASAN reported leaks
Hi,
I'm currently trying to find and fix memory leaks (compiling with
``-fsanitize=address``) in the KLEE tool [1] an having found some
leaks and I'm having trouble suppressing them.
I'm trying to suppress them using the
``-fsanitize-blacklist=blacklist.txt`` option as documented at
[2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6).
The sort of reported leaks I see are
```
2009 Apr 08
2
[LLVMdev] new warnings
/Volumes/SandBox/clang/clang/clang/unittests/VMCore/MetadataTest.cpp:
In member function 'virtual
void<unnamed>::MDNodeTest_Everything_Test::TestBody()':
/Volumes/SandBox/clang/clang/clang/unittests/VMCore/MetadataTest.cpp:
76: warning: dereferencing type-punned pointer will break strict-
aliasing rules
:-(
2011 Jul 24
0
[LLVMdev] Build of latest llvm gives warning and error
Hi Edward,
> Building of llvm with gcc-4.5.2-1 gives these warnings:
>
> 1) Building FileManagerTest
>
> "llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build
> C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp:
> In member function 'virtual
>
2014 Jun 30
2
[LLVMdev] LLD dynamic compilation
Folks,
I'm having a look at LLD and I need some guidance...
I know it's not production ready for x86 and ARM (the idea is to make
it so). My steps:
I've added it to tools/lld and ran CMake again (on x86_64) on a
standard release build (static linking). It works, builds but I see
one unit test error:
Note: Google Test filter = InputGraphTest.Observer
[==========] Running 1 test from
2018 Sep 13
2
New warnings when building trunk with GCC 9
Hello,
GCC 9.0 introduces a new warning checkers and some of them found possible
issues in LLVM.
In file included from
/home/davidbolvansky/trunk/llvm/include/llvm/Analysis/LazyCallGraph.h:38,
from
/home/davidbolvansky/trunk/llvm/unittests/Analysis/LazyCallGraphTest.cpp:10:
/home/davidbolvansky/trunk/llvm/include/llvm/ADT/ArrayRef.h: In
instantiation of
2009 Apr 08
0
[LLVMdev] new warnings
Mike,
Can you please just respond to the specific patch on llvm-commits instead
of emailing llvm-dev?
Thanks,
-Tanya
On Tue, 7 Apr 2009, Mike Stump wrote:
> /Volumes/SandBox/clang/clang/clang/unittests/VMCore/MetadataTest.cpp:
> In member function 'virtual
> void<unnamed>::MDNodeTest_Everything_Test::TestBody()':
>
2013 Apr 01
0
[LLVMdev] cannot compile 3.2, ScalarEvolutionTest fails to link
I am trying to build 3.2 and get this error:
make[2]: Leaving directory `/home/opt/llvm-3.2.src/unittests/ADT'
/home/opt/llvm-3.2.src/unittests/Analysis/Release+Asserts/ScalarEvolutionTest.o:
In function `llvm::(anonymous
namespace)::ScalarEvolutionsTest_SCEVMultiplyAddRecs_Test::TestBody()':
ScalarEvolutionTest.cpp:(.text+0x1408): undefined reference to
2013 Jan 07
2
[LLVMdev] Build failure when building single threaded LLVM with CMake
Hi,
I found that building LLVM in single-threaded mode with CMake is failing
because some object files still have references to pthread routines. There
are two instances of the build failure happening.
$ cmake .../llvm/ -DLLVM_ENABLE_THREADS=0
$ make -j8 check-all
% Linking CXX executable IRTests
../../lib/libgtest.a(gtest.cc.o): In function
2020 Sep 13
2
libva-utils test siuite is crashing in nouveau sriver
Hi,
I'm hitting that issue since Mesa 20.0.6 and it is present still in latest
version 20.1.7
```
[tkloczko at barrel SPECS]$ coredumpctl gdb 3926866
PID: 3926866 (test_va_api)
UID: 1000 (tkloczko)
GID: 1000 (tkloczko)
Signal: 11 (SEGV)
Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago)
Command Line: ./test_va_api
Executable:
2011 Jul 26
3
[LLVMdev] [PATCH][RFC] upgrade to googletest 1.6.0 (was Re: Build of latest llvm gives warning and error)
On 24 July 2011 10:59, Duncan Sands <baldrick at free.fr> wrote:
> Hi Edward,
>
>> Building of llvm with gcc-4.5.2-1 gives these warnings:
>>
>> 1) Building FileManagerTest
>>
>> "llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build
>> C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp:
>> In
2012 Oct 16
0
[LLVMdev] [cfe-dev] cmake+ninja build error for compiler-rt sources
On Sat, Oct 13, 2012 at 1:52 PM, Chandler Carruth <chandlerc at google.com> wrote:
> On Sat, Oct 13, 2012 at 1:09 AM, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com>
>> wrote:
>> > I'm seeing this too. CC'ing the author ubsan stuff.
>> >
>> >
2020 Sep 23
2
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
> On 22/09/2020 21:00 PGNet Dev <pgnet.dev at gmail.com> wrote:
>
>
> On 9/22/20 10:51 AM, Aki Tuomi wrote:
> >>>
> >
> > Well, dovecot does not actually do any parsing for system-wide openssl.cnf. This sounds more like OpenSSL issue than dovecot issue.
>
> I've NO issue with that config/setting with any _other_ app -- whether in general
2012 Oct 13
2
[LLVMdev] [cfe-dev] cmake+ninja build error for compiler-rt sources
On Sat, Oct 13, 2012 at 1:09 AM, David Blaikie <dblaikie at gmail.com> wrote:
> On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com>
> wrote:
> > I'm seeing this too. CC'ing the author ubsan stuff.
> >
> > Richard, I know you were OK with only supporting Clang-bootstraps, but I
> > don't think that's terribly viable