similar to: [LLVMdev] Apple clang 4.2 based on llvm 3.2 produces a wrong "instruction requires:arm-mode"

Moshe, You're more than likely going to get a better response from https://devforums.apple.com/community/tools/xcode llvmdev is a mailing list for the LLVM project which is separate from Xcode development. Cheers, Joe On Jun 12, 2013, at 8:51 AM, Moshe Kravchik <mkravchik at hotmail.com<mailto:mkravchik at hotmail.com>> wrote: Hi, I've got an assembly file which used to

So probably it is a LLVM issue - can anyone from the team look at it and let me know if there is anything to do. Moshe > Date: Wed, 12 Jun 2013 10:53:56 -0700 > Subject: Re: [LLVMdev] Apple clang 4.2 based on llvm 3.2 produces a wrong "instruction requires:arm-mode" > From: t.p.northover at gmail.com > To: mkravchik at hotmail.com > CC: llvmdev at cs.uiuc.edu > >

Hi Moshe, Tim just did tell you what to do :) "Reporting it at llvm.org/bugs (and/or bugreporter.apple.com since that seems to be your platform) would make sure it doesn't get lost." So filing a bug report would be best. -eric On Wed, Jun 12, 2013 at 12:18 PM, Moshe Kravchik <mkravchik at hotmail.com> wrote: > So probably it is a LLVM issue - can anyone from the team

On Thu, Jul 26, 2012 at 12:48 AM, Moshe Kravchik <mkravchik at hotmail.com> wrote: > > Hi, > > I'm looking for a pragma to insert in my source that will turn the > optimization off for that file. Could not find one, it is possible? > > Thanks a lot, > Moshe No, clang does not have a pragma for this. You should use your build system to pass -O0 to clang for this

Hi Moshe, The others are right that you'll likely get better Apple-specific help at the forums, but this problem happens to be the same in generic LLVM. > ./src/asm.s:30:5: error: instruction requires a CPU feature not currently enabled > > add r2, pc, r2 > > According to ARM specification: The specifications you're referring to are a little vague, and the actual

Hi, I encountered an issue with inline assembly in my c files compiled with llvmc. When I have a push instruction in the inline assembly like: __asm__ volatile ( "push {r4}\n\t" ); the compiler will drop the curly braces and leave it in the generated assembly file as: push r4 And this is non-conformant with the ARM

Hi, I'm looking for a pragma to insert in my source that will turn the optimization off for that file. Could not find one, it is possible? Thanks a lot,Moshe -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120726/e713a744/attachment.html>

Hi Philip, > Aside: From the documentation, it's actually unclear how strong a barrier > ISB actually is. The "fetched after the ISB" gives a lot of room for > interpretation. (i.e. is it legal for a cpu to fetch every instruction in a > function, queue them for execution under wait conditions, *then* fetch the > ISB? This would be a *really* weird implementation,

Hi Eric, Following Tim's and your advice I filled the bug:http://llvm.org/bugs/show_bug.cgi?id=16315 Haven't seen any reaction to it from LLVM developers so far. This is the first time I submit a bug to LLVM, maybe I need to set some fields differently to trigger their attention? Moshe > Date: Wed, 12 Jun 2013 13:10:21 -0700 > Subject: Re: [LLVMdev] Apple clang 4.2 based on llvm 3.2

On 7/16/14, 6:09 PM, sgundapa wrote: > I see a couple of issues here. > > If I include .S files for ARM, the –no-integrated-as path complains about > Assembler errors. > > The integrated-as path works fine though. > These are very likely just differences between the old ARM assembler syntax and the new 'Unified' syntax. Can you use an assembler that accepts UAL

> Looks like a problem with llvmc. Your example works fine with clang. llvmc does not do the actual compilation, it executed llvm-gcc / llc. So, it seems problem is there. Anyway, LLVM 2.9 is too ancient, especially for ARM. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello Hal, I am not very familiar with the DSP capabilities of PowerPC, but I imagine there will be instructions for simple vector operations like vector addition, multiplication, etc. so for these I imagine the implementation would consist of just outputting the correct instruction. However, for NEON instructions like the reciprocal step (see

On 24 June 2014 01:55, Philip Reames <listmail at philipreames.com> wrote: > > On 06/19/2014 09:35 AM, Yi Kong wrote: >> >> Hi all, >> >> I'm currently working on implementing ACLE extensions for ARM. There >> are some memory barrier intrinsics, i.e.__dsb and __isb that require >> the compiler not to reorder instructions around their

Stan, Do you mean that you want to emulate the ARM NEON intrinsics on PowerPC? -Hal ----- Original Message ----- > > > Hello LLVM Devs, > > > Thanks for helping me previously to cross-compile for ARM, I managed > to get a working toolchain and am currently having fun compiling > different toy problems and running them on a pandaboard. > > As part of my

Hi guys, I have a question about the LLVM ARM backend: I try to build *.c files for Windows Phone (Windows 8) - so, basically I need to generate an "arm-pe" file (I *think* it has the same file structure like x86-pe file, but i am not sure). unfortunately, LLVM has no support with ARM PE\COFF. Any ideas? How difficult is to add the support in this file format? (LLC can generate ARM

> > Just in case it gets lost in my longer reply, I want to emphasize that if > these will be used to simplify the in-tree backends and those backend > maintainers are on board, then I am *totally* in favor of this going into > the tree. My concerns are heavily based on the fact that as proposed, none > of that seems likely to happen. > > > Framing the problem

On Tue, Mar 4, 2014 at 3:11 PM, Sean Silva <chisophugis at gmail.com> wrote: > On Tue, Mar 4, 2014 at 4:04 PM, Mark Seaborn <mseaborn at chromium.org>wrote: > >> The PNaCl project has implemented various IR simplification passes that >> simplify LLVM IR by lowering complex features to simpler features. We'd >> like to upstream some of these IR passes to

Thank you. I found a partial answer to the problem (1), namely “how to run Clang compiled with LLVM3.6.1 on OS X Yosemite/Xcode6.4" It’s a combination of -isysroot and -resource-dir I’m using these compiler options: "/Users/meister/Development/externals-clasp/build/release/bin/clang" -v \ -resource-dir

Hello LLVM Devs, Thanks for helping me previously to cross-compile for ARM, I managed to get a working toolchain and am currently having fun compiling different toy problems and running them on a pandaboard. As part of my research I am trying to implement the ARM NEON Intrinsics in the PowerPC LLVM backend. I am still at the beginning of my efforts and am not yet familiar with either the ARM or

Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the