similar to: Showcase of the Windows/ARM64/MinGW target

So are you saying that LLVM can be built as ARM64 on Windows now? CMake doesn't show me an option for ARM64 when using MSVC on Windows. I have the latest CMake. On Mon, May 21, 2018 at 2:34 AM, Martin Storsjö via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, > > At the Build conference recently, Microsoft had a session about Windows on > ARM(64), [1]. As case example of

On Mon, 21 May 2018, Hayden Livingston wrote: > So are you saying that LLVM can be built as ARM64 on Windows now? > CMake doesn't show me an option for ARM64 when using MSVC on Windows. > I have the latest CMake. I'm saying that LLVM can produce code for the Windows/ARM64 target. As for compiling LLVM itself to run on ARM64 on Windows, I don't know how to configure MSVC to

Ok. How much work was it to enable ARM64 codegen? Is it is significantly more work than for Linux targets? Are there any special relocations in ARM64 land? On Mon, May 21, 2018 at 3:38 AM, Martin Storsjö <martin at martin.st> wrote: > On Mon, 21 May 2018, Hayden Livingston wrote: > >> So are you saying that LLVM can be built as ARM64 on Windows now? >> CMake doesn't

On Mon, 21 May 2018, Hayden Livingston wrote: > Ok. How much work was it to enable ARM64 codegen? Is it is > significantly more work than for Linux targets? Are there any special > relocations in ARM64 land? It was surprisingly little work, I'd say. Yes, Windows uses COFF, and there's a separate set of relocations for each architecture. Probably not more work than for Linux

On Mon, May 21, 2018 at 3:54 AM Martin Storsjö via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Other than relocations, the main bits were varargs handling, hooking up > small flags and bits here and there as you find what's missing, minor > windows/coff specific details like linker directives and dllimport > handling, and slightly larger things such as stack probing and

hi all ! I have compiled Samba 2.2.2 for Solaris 7 ( Solaris 8 also ) but found out that the "nss_winbind" support is available in source-code, but not after compilation. The neccessary entries in the Makefile after "configre" are missing !! Why ? I have got it to run and it works fine with a small amout of groups. But deploying this samba/winbind version to a Windows

Hi, the second step in my exercice is to calculate the sum of the amout for each class et not the frequency i have this vector x           y 1          100 2          1500 3          3250 4          6250 5          2000 6           450 i want to use the function table and cat to calculate the sum of the amount in each class [0-1000], [1000-3000],[> 3000] Thank you for your help??

On Mar 26, 2014, at 7:55 AM, Peter Robinson <pbrobinson at gmail.com> wrote: > On Wed, Mar 26, 2014 at 11:45 AM, Vinay <vinay.nair at novanet.net> wrote: >> Hi, >> >> I wanted to build opus along with PJSIP for iOS for the architecture arm64. >> I wanted to know if opus supports arm64? > > The opus code builds fine on ARM64 on Linux at least,

Hi, I wanted to build opus along with PJSIP for iOS for the architecture arm64. I wanted to know if opus supports arm64? -- Vinay Nair vinay.nair at novanet.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20140326/e617665a/attachment.htm

I have a question about memory. I have 8GB of RAM on a Dell PE 1850(usb disabled kernel, cos it gets locked up on heavy I/O). My domain0 has only 2 gigs of memory. I have 2 guest domains 512 each. Now when i try to create a 3rd guest domain of 512, xen wont let me do it. My confusion is "Is 4G the max amount of memory a domain can get/ or is 4G the max amout of cumulative memory all the

Hi Renato, >> 2. Test it. Benchmark it. Explore it. Get data for the community to work with about the state of the back end. ARM has some excellent data that will help guide us here. > > Count me in. Would that be a different triple? arm64-linux-gnu? Yep. "--target arm64-linux-gnu" should behave basically the same as aarch64-linux-gnu, except ending up in the ARM64 backend.

Hi, I wanted to build opus along with PJSIP for iOS for the architecture arm64. I wanted to know if opus supports arm64? -- Vinay Nair vinay.nair at novanet.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20140326/8576b64e/attachment-0001.htm

On Sun, Jul 19, 2020 at 5:04 PM Zhenyu Zheng <zhengzhenyulixi@gmail.com> wrote: > > Hi oVirt, > > We are currently trying to make oVirt work on ARM64 platform, since I'm quite new to oVirt community, I'm wondering what is the current status about ARM64 support in the oVirt upstream, as I saw the oVirt Wikipedia page mentioned there is an ongoing efforts to support ARM

I have used the patch to build opus 1.1. Although I have not tried the latest git master, will try that. Will that work for armv7, armv7s and arm64? On Wed, Mar 26, 2014 at 11:01 PM, Martin Storsj? <martin at martin.st> wrote: > On Wed, 26 Mar 2014, Jonathan Lennox wrote: > > >> On Mar 26, 2014, at 7:55 AM, Peter Robinson <pbrobinson at gmail.com> wrote: >>

Hi Hal, > Is a different target triple the right thing to do here? I think that would introduce a ton of user confusion. How about we keep the target triples as they are, and add some other way to choose the desired backend? In the short term, it's almost essential. Both of these targets are going to be existing simultaneously for a while and all the LLVM tools (for testing if nothing

Hi Zengruan, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvmarm/next] [also build test ERROR on kvm/linux-next linus/master v5.5-rc3 next-20191220] [cannot apply to arm64/for-next/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in

On 11/08/2013 09:12 AM, Steve Capper wrote: > + > +/* > + * x19-x28 are callee saved, also save fp, lr, sp. > + * d8-d15 are also callee saved. > + */ > + > +struct __jmp_buf { > + uint64_t __gregs[13]; > + uint64_t __fpregs[8]; > +}; > + Since the index of these arrays have no connection with what is stored in them, they should be named fields in the structure,

Not subscribed to the list, sorry to mess up the message threading - but to touch on one question that was raised earlier in the day, Bob Wilson wrote: > On Mar 28, 2014, at 4:23 PM, Jevin Sweval <jevinsweval at gmail.com> wrote: > >> Is the LLDB patch missing? I only see libc++, compiler-rt, LLVM, and Clang patches > > We have a patch for LLDB but it is combined with a

Hi Chandler, > I'd like to hear from the existing AArch64 backend maintainers if they have > any concerns about getting #1 done right away? I agree (with my AArch64 maintainer hat on). The goal of merging these two backends will hopefully do a lot to make sure the eventual code is better than what exists now in either individual directory; and doing the real work towards that will be

Hello everyone, I made a quick patch to clang/llvm to introduce an "apple_abi" function attribute (https://github.com/aguinet/llvm-project/commit/c4905ded3afb3182435df30e527955031cb0d098), to be able to compile functions for the Apple ARM64 ABI when targeting other ARM64 OSes (e.g. Linux). This can be seen as the Apple version of the already existing "ms_abi" attribute. In