similar to: [LLVMdev] [lld][Windows] Warning during builds

On Sun, Oct 6, 2013 at 8:21 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > C:\Program Files (x86)\Microsoft Visual Studio > 11.0\VC\include\concrt.h(313): warning C4530: C++ exception handler used, > but unwind semantics are not enabled. Specify /EHsc > (C:\lld-x86_64_win7\lld-x86_**64-win7\llvm.src\tools\lld\** >

As part of my effort to replace our hand-rolled mutexes with std::mutex and std::recursive_mutex, I found that many of the tests were failing on Windows after doing the replacement. One of the reasons was due to the use of a mutex in lib\Support\CrashRecoveryContext.cpp. If this mutex is an std::recursive_mutex or std::mutex, tests fail. If this mutex is a windows CRITICAL_SECTION, the tests

Hello everyone, I was wondering what is the status regarding exceptions for the windows-msvc target? The corresponding part of the documentation (llvm/decs/ExceptionHandling.rst) hasn't been updated since 2015, was there any progress since? This is most likely known, but there's significant divergence between the behavior of MSVC cl.exe and clang-cl.exe: Consider: void crash() {

This one includes the latest App.cpp which includes the Mac fix from Nick. I thought it was in 0.0.11, but it wasn''t. It also adds support for "stock objects", like colours, pens, and fonts. This turned out to be quite challenging, but I''m happy with the solution. It only took a few days :-/ Kevin

I just pushed a new wxruby-swig, which includes the known MSWin rakefile changes. It also has some significant internal improvements that will make it easier to add classes, and it includes support for one new class (wxEvent). wxruby-swig is now licensed under the "MIT license". wxRuby will remain under the wxWindows license as long as we are releasing the old code base. When we

RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.1qa2/ SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.1qa2.tar.gz This release is made off jenkins-release-42 -- Gluster Build System

Should "lit :: shtest-format.py" (from check-lit) be marked unsupported on PS4? It seems flakey there. This evening, it failed on my commit, r337514, and I'm fairly confident it wasn't my commit's fault. Then it recovered on the next commit. http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33502

It looks like there are errors in the buildbot runs with std::future_error when executing lot of tests, probably we can disable it for now to make the buildbot clean ? http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-ubuntu-13.04/builds/26755/steps/test/logs/stdio has more information. Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by

Good day, I initially posted this issue on CentOS-mirror a week ago but did not receive any response. I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image. As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2 The checksum

I would like to know approximately the overall execution flow when the guest O/S page fault - how is the page fault transfer to a page fault in the host O/S? Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Dear testers, The final version of 5.0.0 has just been tagged. There were no changes after rc5. Please build the final binaries and upload to the sftp. For those following along: this means 5.0.0 is complete, but it will take a few days to get the tarballs ready and published on the web page. I will send the announcement once everything's ready. Many thanks everyone for your hard work!

I have managed to compile llvm and clang against musl, but it behaves really strange: At first I tried to launch the compiler with musl dynamic loader: $ LD_LIBRARY_PATH=/path/to/musl/lib /path/to/musl/lib/ld-musl-x86_64.so.1 /path/to/llvm/bin/clang -v clang version 4.0.0 (https://github.com/llvm-mirror/clang 40adebeca0f99006d407508653c2cbd270a1a51c) (https://github.com/llvm-mirror/llvm

Brian, Sorry I forgot to switch to plain text. The link is: https://bugs.centos.org/view.php?id=15186# Ed On Saturday, September 8, 2018, 9:56:25 PM EDT, nschehovin--- via CentOS <centos at centos.org> wrote: Brian, There is a kernel bug that seems to affect systems with older Intel processors.? I have a Dell Laptop that on bootup of kernel 2.6.32-754.3.5.el6.x86_64 will

It's pretty weird -- I can't reproduce this on my machine. Can you? I can only speculate a cause. But I'll try to disable the feature to see if buildbot will get back to green. On Thu, Feb 26, 2015 at 9:08 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > It looks like there are errors in the buildbot runs with std::future_error > when executing lot of tests,

Hi, I got an error while compiling the R-devel (R-2.5.0) package under Redhat Linux, but the R-patch package (R-2.4.1) was compiled perfectly fine. The following is what I got from the R-devel package downloaed on Jan. 30th., 2007: ----------------------------------------------------------- >./configure .... R is now configured for x86_64-unknown-linux-gnu Source directory: .

Hi Peter I guess this is the document written by you https://fosdem.org/2018/schedule/event/crosscompile/attachments/slides/2107/export/events/attachments/crosscompile/slides/2107/How_to_cross_compile_with_LLVM_based_tools.pdf I follow it to try to use the clang to do cross compilation. Actually, my target binaries is SPECCPU2006 and autotools based binaries. However, I failed on the first

Hi, 1) From the code it appears that there is no common entry/exit point for the hypervisor calls. Wanted to confirm if this is right? 2) Also is there a per-domain flag to indicate that the hypervisor call is in progress in a particular domain? Thanks, Sowmya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

On Mon, 2014-01-06 at 14:23 -0800, Jim Grosbach wrote: > Hi David, > > AFAIK, the answer is basically “because it’s always been that way.” I > seem to recall there were some things that were different (data layout > string and such), but that could also be parameterized if it hasn’t > been already by the recent refactorings, I suppose. It is *all* now parameterized. The classes

Hi, My grep regex foo is not very good and googling is getting me nowhere so hopefully someone is kind enough to give me some pointers. Goal: grep (non .dbg) filenames and versions from a ftp dir listing and a raw html file: $ wget --no-remove-listing -O ftp-index.txt ftp://127.0.0.1/test/ $ wget --no-remove-listing -O index.html http://127.0.0.1/test/ The relevant parts of the files above

While attempting to troubleshoot a problem with PCI passthrough, I noticed a number of facts that, when considered together, may indicate a serious upgrade path issue with regard to Xen and QEMU: 1. libxen-dev is a single package with two versions: a 4.8 version and a 4.11 version 2. libxen-dev version 4.8 produces libraries with 4.8 in the soname. A qemu compiled against this version has