similar to: Very silent R

Displaying 20 results from an estimated 8000 matches similar to: "Very silent R"

2015 Jul 21
4
[LLVMdev] DebugInfo/PDB/pdbdump-symbol-format.test fails with VS 2015
Hi, This might be interesting since it seems to be the only LLVM test failing with VS 2015: FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) ******************** TEST 'LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** Script: -- llvm-pdbdump -symbols C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb |
2015 Jul 21
0
[LLVMdev] DebugInfo/PDB/pdbdump-symbol-format.test fails with VS 2015
FWIW, this test is passing for me on Windows 7 with Visual Studio 2015 (debug build). 59> Running all regression tests 59> -- Testing: 23734 tests, 32 threads -- 59> 59> Testing Time: 634.19s 59> Expected Passes : 22821 59> Expected Failures : 160 59> Unsupported Tests : 753 59> lit.py: lit.cfg:195: note: using clang:
2015 Jul 23
1
[LLVMdev] DebugInfo/PDB/pdbdump-symbol-format.test fails with VS 2015
Ok just tried on Win 7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is
2016 Jan 15
2
Building SVN head with CMake - shared libraries?
On Fri, Jan 15, 2016 at 11:05 AM, Ismail Donmez <ismail at i10z.com> wrote: > Hi, > > On Fri, Jan 15, 2016 at 12:59 AM, Chris Bieneman <beanz at apple.com> wrote: >> I’m kinda scared that you’re using it. What are you trying to accomplish >> that you are using it? Generally having LLVM split among that many >> dynamically loaded libraries results in
2016 Jul 20
2
Hitting assertion failure related to vectorization + instcombine
Hi folks, I'm hitting the below assertion failure when compiling this small piece of C code (repro.c, attached). My command line is: bin/clang --target=aarch64-linux-gnu -c -O2 repro.c clang is built from top of trunk as of this morning. It only happens at -O2, and it doesn't happen with the default target (x86_64). I tried to reproduce using just 'llc -O2' but didn't
2016 Jul 20
2
Hitting assertion failure related to vectorization + instcombine
Thanks for notifying me. Yes, this was a recent change. Taking a look now. On Wed, Jul 20, 2016 at 1:49 PM, Michael Kuperstein <mkuper at google.com> wrote: > +Sanjay, who touched this last. :-) > > On Wed, Jul 20, 2016 at 12:44 PM, Ismail Badawi (ibadawi) via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi folks, >> >> I'm hitting the
2016 Jul 22
2
Hitting assertion failure related to vectorization + instcombine
Sanjay: let me know if this is something that will apply to 3.9. Thanks, Hans On Wed, Jul 20, 2016 at 5:59 PM, Sanjay Patel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Quick update - the bug existed before I refactored that chunk in > InstSimplify with: > https://reviews.llvm.org/rL275911 > > In fact, as discussed in https://reviews.llvm.org/D22537 - because we have a
2016 Jul 25
2
Hitting assertion failure related to vectorization + instcombine
Sure. David, what do you think about merging this to 3.9? Sanjay: are you saying I'd just apply that diff to InstructionSimplify.cpp, not InstCombineSelect.cpp? On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: > Hi Hans - > > Yes, I think this is a good patch for 3.9 (cc'ing David Majnemer as code > owner). The functional change was
2016 Oct 13
2
Status of docs/BitCodeFormat.rst?
I think it just changed formats which prompted a change in ID -- the code now uses TYPE_BLOCK_ID_NEW (= 17). I haven’t looked deeply to see how different it is. Ismail > On Oct 13, 2016, at 2:02 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > >> On Oct 13, 2016, at 10:24 AM, Ismail Badawi (ibadawi) via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>
2014 Mar 26
7
[LLVMdev] Lots of regtest failures on PPC64/Linux
Hi, Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash with a backtrace like: [ 3149s] -- [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 __kernel_sigtramp_rt64 + 0 [ 3149s] 4
2016 Jun 28
3
ENABLE_TIMESTAMPS and update to CMake v3.5.2
I am in the middle of the fun and games of updating my out-of-tree sources to the LLVM head revisions, and after updating to CMake v3.5.2 I am now getting a warning that 'ENABLE_TIMESTAMPS' is being ignored. Has support for embedding the timestamp in the build been removed or is there a new way of configuring it? I generally build internal transitional builds with this enabled so that
2016 Jun 28
0
ENABLE_TIMESTAMPS and update to CMake v3.5.2
Hi, On Tue, Jun 28, 2016 at 3:25 PM, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I am in the middle of the fun and games of updating my out-of-tree sources > to the LLVM head revisions, and after updating to CMake v3.5.2 I am now > getting a warning that ‘ENABLE_TIMESTAMPS’ is being ignored. > > > > Has support for embedding the timestamp
2013 Nov 22
3
[LLVMdev] [3.4 branch] SystemZ regressions
Hi, On Thu, Nov 21, 2013 at 8:16 PM, Richard Sandiford < rsandifo at linux.vnet.ibm.com> wrote: > İsmail Dönmez <ismail at donmez.ws> writes: > > Using openSUSE 13.1 on s390x machine I get two new regressions with llvm > > 3.4rc1: > > Hmm, I don't see this locally. Just to rule out one possibility, > which compiler are you using to build? Do you see the
2014 Mar 26
3
[LLVMdev] Lots of regtest failures on PPC64/Linux
----- Original Message ----- > From: "Renato Golin" <renato.golin at linaro.org> > To: "İsmail Dönmez" <ismail at donmez.ws> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, March 26, 2014 8:14:18 AM > Subject: Re: [LLVMdev] Lots of regtest failures on PPC64/Linux > > Hi Ismail, > > Is
2017 Aug 02
2
ubsan no longer compiles when libc++ is the default
Hi, I see the following variables in the CMakeCache.txt: SANITIZER_CXX_ABI:STRING=default //STRINGS property for variable: SANITIZER_CXX_ABI SANITIZER_CXX_ABI-STRINGS:INTERNAL=none;default;libcxxabi;libstdc++ Regards, ismail On Tue, Aug 1, 2017 at 7:32 PM, Vedant Kumar <vsk at apple.com> wrote: > >> On Aug 1, 2017, at 7:07 AM, İsmail Dönmez via llvm-dev <llvm-dev at
2015 May 07
2
[LLVMdev] Recent libc++ failures due to libunwind
Hi, During last 2-3 days I started to get some new regressions from the libc++ testsuite, one of them is std/containers/sequences/list/list.modifiers/insert_iter_iter_iter.pass.cpp . When run under gdb this seems to be a crash under libunwind code: Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007ffff73d00ce in
2012 Apr 17
2
[LLVMdev] compiler_rt fails to build in release_31 branch
Hi; This is on Linux/x86-64, I get this at stage1: make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' Makefile:6: make/config.mk: No such file or directory Makefile:7: make/util.mk: No such file or directory Makefile:16: *** Refusing to build with empty ProjObjRoot variable. Stop. make[2]: Leaving directory
2015 Feb 19
3
[PATCH] Unbreak compilation with --without-ssh1
Hi, Patch attached for $SUBJECT. ismail
2015 Jan 23
9
[Bug 2343] New: test_fuzz.c won't compile if ssh1 support is disabled
https://bugzilla.mindrot.org/show_bug.cgi?id=2343 Bug ID: 2343 Summary: test_fuzz.c won't compile if ssh1 support is disabled Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Build system Assignee:
2016 Jul 27
0
Hitting assertion failure related to vectorization + instcombine
David, Sanjay: ping? On Mon, Jul 25, 2016 at 11:07 AM, Hans Wennborg <hans at chromium.org> wrote: > Sure. David, what do you think about merging this to 3.9? > > Sanjay: are you saying I'd just apply that diff to > InstructionSimplify.cpp, not InstCombineSelect.cpp? > > On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: >> Hi