search for: arch64

I am trying to cross compile an assembly file using clang but with " -fno-integrated-as" so that clang does not use its own assembler. Clangs calls the command: /usr/bin/aarch64-linux-gnu-as -o Myfile.o Myfile.s but it fails because of missing *-march=armv8-a+crypto *which is required to build build my source file Myfile.s I am passing "-march=armv8-a+crypto" to clang command but how do i promote the same flag to assembler arch64-linux-gnu-as through clang? --...

I am trying to build chromium and at this moment, They see some issues with internal one so recommended to use the flag -fno-integrated-as. Here is my exact build command (with -v and --save-temps): $ clang -Igen -I../../include -target aarch64-linux-gnu -march=armv8-a+crypto -fno-integrated-as --sysroot=./debian_jessie_arm64-sysroot -O2 -c MyFile.S -o MyFile.o -v --save-temps clang version 3.8.0 (trunk 247874) Target: aarch64--linux-gnu Thread model: posix Found candidate GCC installation: ./src/build/linux/debian_jessie_arm64-sysroot/u...

...) [/wine-git/dlls/dsound/dsound.c:855] in dsound (0x0032f314) I filed a bug report about it here : http://bugs.winehq.org/show_bug.cgi?id=29431 , yet because I don't see any other users reporting major sound crashes like this one, I wonder if the issue has something to do with my system. I use Arch64, and I have all the mandatory and optional lib32 dependencies for wine on Arch. Do any other Arch64 users experience this? If not, what do you suggest to fix this? Any suggested workarounds? Thanks!

Anyone tried using g++ 4.2.1 to build llvm yet? 4.2 has at least one serious bug that's a showstopper. -Dave

...-Dave > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > I compiled llvm from svn trunk with gcc 4.2.1 (arch64 linux) last night. had no problems. I only compiled the llvm library not llvm-gcc.

Hi, so here it is, LZ4 compression method inside btrfs. The patchset is based on top of current Chris'' for-linus + Andi''s snappy implementation + the fixes from Li Zefan. Passes xfstests and stresstests. I haven''t measured performance on wide range of hardware or workloads, rather wanted to publish the patches before I get distracted again. I''d like to ask

...t timed out in thread 0009, blocked by 0023, retrying (60 sec) and a Visual C++ runtime error in wine saying that it had terminated bla bla. I once got it to run, I made absolutely NO CHANGES to it, but it ran. Then I loaded it again after closing it and I got the exact same error. I am running arch64 so I'm using the Wine-1.1.13-2 binary from the openSUSE repository, it works great in uTorrent and in steam but I can't play CS or CS:CZ. Glxgears runs great, Google Earth runs great, uTorrent runs great. I don't know where to start, google didn't help. Any ideas? :o

Hello, I have Lenovo thinkpad R61i. I am beginer in Linux (Curently I have Arch64). In this computer is Intel Graphics Media Accelerator X3100. Drivers are runing corectly (momentaly don't works accelerated kwin and compiz, but on Ubuntu works). I think this can be good card for some "small playing", but I have a big problem with wine. On every distribution what I...

hello! i am using archlinux x86_64. i have got a 32bit chroot and also 32bit libs installed, so i can run 32bit apps inside the chroot or using the libs. now my problem: my native desktop resolution is 1680x1050. i want to play my games in 800x600, 1024x768 or whatever. when i run a game in the chroot, it works like a charme, wine changes the resolution and i have no problems at all. when i run

...crashes and I have to manually kill the process. Downgrading to wine 1.3.26 I can play again fine. Athlon64-X2 Nvidia geforce 450 GTS Arch linux 64 (using the 32bit wine version) If it helps here is the output on the console. Regards ------------------------------------------------ [morgan at arch64 paintball2]$ env WINEPREFIX="/home/morgan/games/civ5" wine C:\\Program\ Files\\Steam\\Steam.exe fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub. err:ntlm:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in yo...

...it would be preferred to have a mangling scheme > >> that is based on (and standardized by) OpenMP. > > > > I still think it will be required to have a standardized one, not > > only preferred. > > > > > > I am all with you in standardizing. x86 and arch64 have their own > vector function ABI, which, although “private”, are to be considered > standard. Opensource and commercial compilers are using them, > therefore we have to deal with this mangling scheme, whether or not > OpenMP comes up with a standard mangling scheme. I don't get...

...scheme > > >> that is based on (and standardized by) OpenMP. > > > > > > I still think it will be required to have a standardized one, not > > > only preferred. > > > > > > > > > > I am all with you in standardizing. x86 and arch64 have their own > > vector function ABI, which, although “private”, are to be considered > > standard. Opensource and commercial compilers are using them, > > therefore we have to deal with this mangling scheme, whether or not > > OpenMP comes up with a standard mangling...

...a scalar version to a vector one. It builds also the vector version definition by auto-vectorizing the body of the scalar function. I don’t know if the patches related to VecClone also are intended to use the `vector-variant` attribute for function declaration with a #pragma omp declare simd. On aarch64, in Arm compiler for HPC, we do that to support vector math libraries. It works in principle, but `vector variant` allows more context selection (and custom names instead of vector ABI names, which are easier for users). > > On 05/31, Francesco Petrogalli wrote: >>> On May 31, 201...

...version to a vector one. It builds also the vector version definition by auto-vectorizing the body of the scalar function. > > I don’t know if the patches related to VecClone also are intended to use the `vector-variant` attribute for function declaration with a #pragma omp declare simd. On aarch64, in Arm compiler for HPC, we do that to support vector math libraries. It works in principle, but `vector variant` allows more context selection (and custom names instead of vector ABI names, which are easier for users). > > > > > > On 05/31, Francesco Petrogalli wrote: > &g...

...a vector one. It builds also the vector version definition by auto-vectorizing the body of the scalar function. > > > > I don’t know if the patches related to VecClone also are intended to use the `vector-variant` attribute for function declaration with a #pragma omp declare simd. On aarch64, in Arm compiler for HPC, we do that to support vector math libraries. It works in principle, but `vector variant` allows more context selection (and custom names instead of vector ABI names, which are easier for users). > > > > > > > > > > On 05/31, Francesco Petro...

...preferred to have a mangling scheme > that is based on (and standardized by) OpenMP. I still think it will be required to have a standardized one, not only preferred. > I hear the argument on having some common ground here. In fact, there > is already common ground between the x86 and aarch64 backend, who have > based their respective Vector Function ABI specifications on OpenMP. > > In fact, the mangled name grammar can be summarized as follows: > > _ZGV<isa><masking><VLEN><parameter type>_<scalar name> > > Across vector extensions...

>/ these are the packages installed:/ > >/ ii linux-image-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch1 / >/ Linux 2.6.18 image on AMD64/ >/ ii linux-modules-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch1 / >/ Linux 2.6.18 modules on AMD64/ >/ ii xen-hypervisor-3.2-1-amd64 3.2.0-2 / >/ The Xen Hypervisor on

...at can be used when / if needed. As someone as suggested, we should use a custom attribute. Because the mangling scheme of the Vector Function ABI provides all the information about the shape and properties of the vector function, I propose the approach exemplified in the following code: ``` // AArch64 Advanced SIMD compilation double foo(double) __attribute__(simd_variant(“nN2v”,”neon_foo”)); float64x2_t neon_foo(float64x2_t x) {…} // x86 SSE compilation double foo(double) __attribute__(simd_variant(“aN2v”,”sse_foo”)); __m128 sse_foo(__m128 x) {…} ``` The attribute would use the “core” tokens...

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I have laid some groundwork. Sadly...