search for: x86_

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\** > lib\ReaderWriter\ELF\Hexagon\**HexagonLinkingContext.cpp) > [C:\lld-x86_64_win7\lld-x86_**64-win7\llvm.obj\tools\lld\** > lib\ReaderWriter\ELF\Hexagon\**lldHexagonELFTarget.vcxproj] > C:\Program Files (x86)\Microsoft Visual Studio > 11...

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\lib\ReaderWriter\ELF\Hexagon\HexagonLinkingContext.cpp) [C:\lld-x86_64_win7\lld-x86_64-win7\llvm.obj\tools\lld\lib\ReaderWriter\ELF\Hexagon\lldHexagonELFTarget.vcxproj] C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\concrt.h(313): warning...

...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 of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9...

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

...:: 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 <http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33502> http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33503 <http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu...

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 the Linux Foundation

...ankar 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, 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 the Linux Foundation > > -------------- next part -------------- An HTML attachment was...

...eems to fail very infrequently > though. > > > 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 > > http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_ > 64-scei-ps4-ubuntu-fast/builds/33503 > > > >> On Jul 19, 2018, at 17:59, llvm.buildmaster at lab.llvm.org wrote: > >> > >> The Buildbot has detected a new...

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

...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: . Installation directory: /usr/local C compiler: gcc -std=gnu99 -g -O2 Fortran 77 compiler: g77 -g -O2 C++ compiler: g++ -g -O2 Fortran 90/95 compiler: gfortran -g -O2 Obj-C compiler: Inter...

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 943496ffc4e7cb9d7dd6f5119325a7583e2cc31f) Target: x86_64-pc-linux-musl Thread model: posix InstalledDir: /path/t...

...s.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 display a white square in the upper left corner of the screen and halt.? If I roll back to the 2.6.32-696.30.1.el6.x86_64 version kernel all is well. More info at 0015186: Cannot boot with kernel-2.6.32-754.3.5.el6.x86_64 - CentOS Bug Tracker | | | |? |? | | | | |? | 0015186: Cann...

...ed on the first step. I write a hello world as test.c. I refer to your document and download the newest version of arm toolchain. I use the following command to try to compile the code to binary. sudo /home/jmh/Downloads/llvm/build/bin/clang --sysroot=/home/jmh/Downloads/gcc-linaro-7.3.1-2018.05-x86_64_arm-linux-gnueabi/arm-linux-gnueabi/libc --gcc-toolchain=/home/jmh/Downloads/gcc-linaro-7.3.1-2018.05-x86_64_arm-linux-gnueabi/lib/gcc/arm-linux-gnueabi/ -target arm-linux-gnueabi -fuse-ld=lld -L /home/jmh/Downloads/llvm/build/lib -I/home/jmh/Downloads/llvm/build/include/ --rtlib=compiler-rt -o t...

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

...control panel creates the domain. Later, domain can simply the corresponding entry to issue a hypercall. For the subroutine of the HYPERVISOR_xxx, usually it is do_xxx. For example, __HYPERVISOR_sched_op should be do_sched_op. For more information, please refer to hypercall_table in xen/arch/x86/x86_{32,64}/entry.S. Thanks Ke T S wrote: > Hi, > > Can someone let me know what exactly the array "hypercall_page " > contains? Are they function pointers? > > How do I know which functions are going to be called when a > HYPERVISOR_xxx is called? > > For insta...

...es plain Unix filenames in Wine applications? I need to cross compile PostgreSQL and some third party modules on my Fedora 15 system to 64-bit Windows. PostgreSQL uses its "pg_config" for 3rd party code to tell the include dir, compile flags, etc: [zozo at localhost postgis-1.5.3]$ /usr/x86_64-w64-mingw32/sys-root/mingw/bin/pg_config.exe --pgxs Z:/usr/X86_~FWL/sys-root/mingw/lib/POST~SMW/pgxs/src/MAKE~WLE/pgxs.mk This path doesn't exist as is but "winepath --unix" can convert it to a more useful one. Is there an environment variable or a winecfg setting so applications...

...which correctly reproduces the RFC 4578 (no conflict), and adds: 6 EFI IA32 <- used by many vendors for legacy boot of x64 machine 7 EFI BC <- used by many vendors for EFI x64 boot So, I have some questions: 1_ Which Architecture Type value "should" correspond to (U)EFI (x86_)x64? 2_ Isn't this conflicting information "messing" what vendors are supposed to set/follow? 3_ Is there older (U)EFI hardware following one convention and newer (U)EFI hardware following another? 4_ In practical terms, what would be an "adequate" way to solve th...

...ed myself and read carefully through the entire thread that I found this solution. Here is the procedure spelled out a bit more precisely. Get the CentOS 5.2 rpms of popt, rpm, rpm-libs, rpm-python and rpm-build. Obviously you can use most any mirror and if you are using i386 you should replace x86_64 with i386. I prefer to use RIT since its my Alma Mater and they seem to have good bandwidth and keep older versions. # wget http://mirrors.rit.edu/centos/5.2/os/x86_64/CentOS/popt-1.10.2-48.el5.x8 6_64.rpm # wget http://mirrors.rit.edu/centos/5.2/os/x86_64/CentOS/rpm-4.4.2-48.el5.x86_ 64.rpm #...

...ere 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 are identical apart from that one true/false... > > @@ -74,7 +75,7 @@ X86_32TargetMachine::X86_32TargetMachine(const Target &T, Stri > > const TargetOptions &Options, > > Reloc::Model RM, CodeModel::Model CM, > > CodeGenOpt::...