similar to: LLVM on Windows ARM

Displaying 20 results from an estimated 4000 matches similar to: "LLVM on Windows ARM"

2018 Mar 01
0
LLVM on Windows ARM
On Thu, Mar 1, 2018 at 1:26 AM Hayden Livingston via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Does LLVM compile on ARM windows machines? More importantly, can LLVM > generate code on Windows ARM? And lastly can it be hosted on Windows > ARM so as to act like a JIT compiler for ARM? Partially. LLVM can target Windows ARM. One big caveat: I’ve only added support for
2017 Feb 05
2
Clang 5.0 support for armv8 64 bit with neon and auto vectorization
On Fri, Feb 3, 2017 at 12:03 PM, Renato Golin <renato.golin at linaro.org> wrote: > Adding some people that know about libcxx and/or windows on arm. > Note that if you are trying to use Windows on ARM port, I've not tested C++ support with MS ABI, onlly the itanium ABI has been tested (there are known limitations for the C++ MS ABI on Windows ARM). Furthermore, we do not
2016 Jul 04
2
Status of stack walking in LLVM on Win64?
> Message: 3 > Date: Sun, 3 Jul 2016 17:49:50 -0700 > From: Michael Lewis via llvm-dev <llvm-dev at lists.llvm.org> > To: Hayden Livingston <halivingston at gmail.com> > Cc: llvm-dev <llvm-dev at lists.llvm.org> > Subject: Re: [llvm-dev] Status of stack walking in LLVM on Win64? > Message-ID: > <CAEm7p3svyOi6JU6r_RCCtRfGhTgTHeRw-SR0iD+9Edv2pi71Dw at
2014 Jun 23
4
[LLVMdev] Support for Windows Phone 8.1
On Wed, Jun 18, 2014 at 10:25 AM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Wed, Jun 18, 2014 at 9:09 AM, Damanjit Singh <dsingh at adobe.com> wrote: > >> Hi Saleem, >> >> Though a simple app works great I am facing few issues trying to link a >> slightly complex object file, generated via LLVM, with some libs generated >> via
2015 Apr 24
3
[LLVMdev] unwind move *NOW*
Greetings, As previously mentioned, the unwind contents are going to be moved today. Im working on this now. If you could please hold off any commits to the Unwind part of things, it would be greatly appreciated. See you on the new layout! -- Saleem Abdulrasool compnerd (at) compnerd (dot) org -------------- next part -------------- An HTML attachment was scrubbed... URL:
2015 Jan 31
2
[LLVMdev] unwind's permanent residence
On Fri, Jan 30, 2015 at 4:12 PM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Fri, Jan 30, 2015 at 3:35 PM, Dan Albert <danalbert at google.com> wrote: > >> Shouldn't it just use the default unwinder for the given platform? >> > > Sure, but what is the default unwinder for a given platform? > > Lets go with Linux. I have two different
2016 Jul 04
3
Status of stack walking in LLVM on Win64?
 > These is metadata for epilogues (UWOP_EPILOG) but it is only available on Windows 8.1 and newer. I'm aware of this. I believe it is so sampling profilers can walk the kernel stack including through paged code -- i.e. the epilogue data is not paged, while the related epilogue code might be. Do you see it used, i.e. in usermode?  (where the pdata/xdata/code are all equally paged). It
2014 Jun 08
2
[LLVMdev] Code generation support in llvm for windows phone
Thank you so much Saleem, The target is Windows phone 8.1 (ARM). I'll update the crash details tomorrow. One big problem is that I have to use a physical windows phone for execution. I wonder if it is possible to execute such "exes" using qemu. Regards, Kashyap On Sun, Jun 8, 2014 at 2:53 AM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Sat, Jun 7, 2014 at
2015 Apr 22
4
[LLVMdev] unwind's permanent residence
On Wed, Apr 22, 2015 at 5:12 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 22 April 2015 at 03:40, Saleem Abdulrasool <compnerd at compnerd.org> wrote: >> So after a bit of a hiatus (sorry, other stuff has been eating up my free >> time), Id like to pick this up again. I think that its a matter of just >> copying the unwind sources into the right
2014 Jun 18
2
[LLVMdev] Support for Windows Phone 8.1
Hi Saleem, Though a simple app works great I am facing few issues trying to link a slightly complex object file, generated via LLVM, with some libs generated via Visual Studio - 1. Seems IMAGE_SCN_MEM_16BIT is only written for the the first header in the COFF file, thus functions in other headers (if you are using function sections) don’t work. I was able to workaround this by forcing this entry
2015 Jan 31
0
[LLVMdev] unwind's permanent residence
On Fri, Jan 30, 2015 at 4:15 PM, Dan Albert <danalbert at google.com> wrote: > On Fri, Jan 30, 2015 at 4:12 PM, Saleem Abdulrasool <compnerd at compnerd.org > > wrote: > >> On Fri, Jan 30, 2015 at 3:35 PM, Dan Albert <danalbert at google.com> wrote: >> >>> Shouldn't it just use the default unwinder for the given platform? >>> >>
2018 Jan 04
8
Linker Option support for ELF
Hello all, There was some interest from a number of a few people about adding support for embedded linker options to ELF. This would be an extension that requires linker support to actually work, but has significant prior art with PE/COFF as well as MachO both having support for this. The desire here is to actually add support to LLVM to pass along the necessary information into the object
2019 Jun 27
2
A libc in LLVM
On Thu, Jun 27, 2019 at 2:05 PM Chris Lattner <clattner at nondot.org> wrote: > Saleem, Owen, others on the thread who are concerned about this: it seems > that some of the concern is that the project goals are too narrow, and thus > the eventual result may not serve the full community well over time. > > Would any of you be interested in what we should consider as the list
2015 Feb 05
3
[LLVMdev] unwind's permanent residence
On Tue, Feb 3, 2015 at 4:07 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 30 January 2015 at 20:43, Jonathan Roelofs <jonathan at codesourcery.com> > wrote: > > Last time we brought this up, there was only partial consensus, and then > > someone arbitrarily declared total consensus (without compelling > arguments > > in any particular direction)
2015 Jan 30
2
[LLVMdev] unwind's permanent residence
On 30 Jan 2015 21:24, "Saleem Abdulrasool" <compnerd at compnerd.org> wrote: > The library is agnostic of the unwinder, the driver is who cares (as it needs to generate the linker invocation). I think that adding a flag to control that similar to -rtlib is probably what we may have to do then. What about the default unwinder for Compiler-RT? Should we assume our own?
2014 Sep 06
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
On Fri, Sep 5, 2014 at 11:32 AM, Jonathan Roelofs <jonathan at codesourcery.com > wrote: > Sergey, > > Not that it'll save you much hassle, but here's an implementation of > __aeabi_idiv0 and __aeabi_ldiv0 that I've been sitting on for a while. > > I vaguely remember compnerd suggesting that I don't commit them to > compiler_rt, but I don't remember
2014 Jun 09
2
[LLVMdev] Support for Windows Phone 8.1
Thanks a lot Saleem, The issue is fixed and a simple app works fine now. -Daman On 08/06/14 12:57 pm, "Nick Lewycky" <nicholas at mxc.ca> wrote: >Damanjit Singh wrote: >> Thanks Saleem, Nick. >> >> I will try with the latest code and share the results. >> >> Though, just curious if I need to really use clang to generate the >> object file
2015 Jan 30
2
[LLVMdev] unwind's permanent residence
On Fri, Jan 30, 2015 at 3:10 PM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Fri, Jan 30, 2015 at 1:41 PM, Renato Golin <renato.golin at linaro.org> > wrote: > >> What about the default unwinder for Compiler-RT? Should we assume our >> own? Gcc's? Assuming nothing will break compilation, since the libraries >> won't be available...
2019 Jun 28
2
A libc in LLVM
On Thu, Jun 27, 2019 at 4:58 PM Saleem Abdulrasool <compnerd at compnerd.org> wrote: > For what it is worth, I do believe that these files do really belong in > the libc project because they are so intricately tied to the implementation > of the language. I just think that the fact these files will be part of > the project is merely an implementation detail and should not even
2014 Oct 05
6
[LLVMdev] lld coding style
In spite of this possibly raising a holy war, I thought I would bring up this question again. When switching between a couple of LLVM repositories, I find having to switch between coding styles a bit of an annoyance. It always takes me a while to get adjusted when switching between LLVM (or clang) and lld. While not an absolute show stopper, not having such friction would be nicer. I realize