similar to: compiler-rt for arm-none-eabi targets

On 18 April 2016 at 16:18, Silviu Baranga <Silviu.Baranga at arm.com> wrote: > This doesn't look like something ACLE specific (I can't find it in the ACLE doc). Sorry, I didn't mean it was ACLE, only that you guys were fiddling with macros. :) > This seems to be a generic macro. I think it would make sense to define it > if we know we're emitting ELF. Since the

On 18 April 2016 at 16:33, Silviu Baranga <Silviu.Baranga at arm.com> wrote: > Doing a grep "eabi" * -R | grep darwin in llvm I found the test divmod-eabi.ll > which uses the triple armv7-apple-darwin-eabi. What format does that have? Certainly not ELF. :) But I didn't mean "has eabi on triple", but "is in none-eabi mode", which may have to check a

On 16 April 2016 at 01:44, Zhao, Weiming via cfe-dev <cfe-dev at lists.llvm.org> wrote: > I'm building libunwind for ARM baremetal using clang. > I notice that __ELF__ is used in libunwind and the macro is only defined for > Linux target on ARM. > Should we also predefine that for arm-none-eabi target? Do you mean in Clang's ARMTargetInfo::getTargetDefines() ? I think

Hi I am cpmpile speex using arm-none-eabi-gcc. All files are from STM32F10xxx Speex library firmware provided by ST. The following files I using is under "STM32F10x_Speex_Lib/STM32/libspeex/gcc": filters_cortexM3.h, filters_cortexM3.s, ltp_cortexM3.h, ltp_cortexM3.s, vq_cortexm3.s. When files were compiled, many errors occurred: many functions are undefined, such as

Hi, Is there a way to (cross-)build the compiler-rt for an ARM-EABI target? I read the comments in the associated Makefile, so I understand it cannot be easily done when builing clang. However, is there a way to build the compiler-rt for another plaftorm but the host, once clang & llvm have been successfully built? Thanks, Manu.

On 09/09/2016 04:31 PM, Stephen Canon wrote: > Gating this on -Owhatever is dangerous, . We should simply default to the pragma “on” state universally. Why so? [honestly asking, not arguing] My guess: b/c we don`t want programs to give different results when compiled at different "-O<...>" settings with the exception of "-Ofast". At any rate, the above change is

> > Why ? I thought you set moodle to use ldaps against AD, so what do you need zentyal for? They installed zentyal and set up a DC to work online with moodle. Imagine if our internet link goes down and students can't authenticate with moodle. I say this because I work in a school in a city in the interior of my state, and the connection is still a little precarious. But the main

I am in a precarious spot.... I run centos 4.0. I upgraded my mod_perl RPM to mod_perl 2.0.1. CGI.pm 3.10 (3.05 comes with centos 4.0) fixes some namespace issues with mod_perl vs mod_perl 2.0.1. I need to upgrade to it to 3.10. Yet that file belongs to the perl rpm that comes with centos. What do people generally do in this type of situation? Do I need to compile a new perl just to upgrade

Dear sir, Thanks for your reply. I apologize for taking a few days to reply. > Crashed how? Please see the below. > Have you turned on ASan? Not yet, but thanks for the suggestion. I guess I will try to rebuild my modified Clang+LLVM with addr. san. and see what happens. > I recommend attaching a minimal reproduction... Well, since I`m hacking on LLVM itself, this is not

Dear all, In the process of trying to add optimization for better layout of global variables, I have run up against a roadblock: I don`t seem to be able to sort the contents of a "SymbolTableListTraits<GlobalVariable>" -- or even swap two elements in that list -- without causing LLVM to crash. I have tried writing a comparator class and then using "llvm::iplist<

Hello, I am trying to mount a lustre filesystem thru an ib2ip gateway. The MDS''s have infiniband connections. The client nodes are tcp/ip connections. I am able to route between the client nodes and the MDS''s. I have the following in /etc/fstab: abe-mds1 at o2ib0,abe-mds2 at o2ib0:/home/client /abehome lustre _netdev,flock 0 0 I get the following when trying

I'm facing a problem with functions arguments. ARM EABI defines that 8-bytes arguments must be 8-bytes aligned. For example: void @f(i32 %a, i64 %b) ARM EABI: r0 <- %a r2,r3 <- %b Darwin: r0 <- %a r1,r2 <- %b void @g(i32 %a, i32 %b, i32 %c) ARM EABI or Darwin: r0 <- %a r1 <- %b r2 <- %c The problem is: I can't differ a i64 argument of two i32 arguments in

Attached is a port of the new ARM eabi from gcc 4.1 to the llvm-gcc branch. With this patch I am able to bootstrap the 4.0 branch using the new eabi. The llvm-gcc branch fails with ------------------------------------ internal compiler error: in prune_unused_types_update_strings, at dwarf2out.c:14372 ------------------------------------ But I believe that this is an unrelated problem and I will

On Feb 8, 2007, at 10:46 AM, Lauro Ramos Venancio wrote: > I'm facing a problem with functions arguments. ARM EABI defines that > 8-bytes arguments must be 8-bytes aligned. For example: > > void @f(i32 %a, i64 %b) > > ARM EABI: > r0 <- %a > r2,r3 <- %b Ok. I suppose this makes it easier to use 64 bit store instructions. > > Darwin: > r0 <- %a >

On Mon, Dec 09, 2013 at 01:58:29PM +0000, Renato Golin wrote: > I can see the error, and it's just a bad selection of choices. I was > wrong in assuming that the "eabi" at the end would always force it: > > $ clang -target arm-elf-eabi -S mod.c -o - | grep mod > .file "mod.c" > bl __modsi3 > bl __umodsi3 I was discussing this with Tim on IRC and he

On Mon, Dec 09, 2013 at 07:56:26AM +0000, Tim Northover wrote: > Hi Joerg, > > > At the moment, this will call __modsi3 and __umodsi3, even though those > > functions are not part of AAPCS. Should this be considered a lowering > > bug in the ARM target? > > LLVM actually supports both variants, depending on the target. The > __aeabi_* functions are part of the

Dear all, I am using initramfs and from the kernel document, I know klibc. So i decide to use it. We are working on marvell pxa310 (bought from Intel), and with the tools chain from marvell, I comple klibc as follows: klibc-1.5> ln -s /home/zjujoe/svn/mhlv_2.6/working/songlixin/20081007_kernel_tflashupdate/ linux klibc-1.5>cat 1.sh export KLIBCARCH=arm export

On 9 December 2013 11:51, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > Part of the concern is that the same code using / does call __aeabi_idiv > and __aeabi_uidiv. Hi Joerg, I can see the error, and it's just a bad selection of choices. I was wrong in assuming that the "eabi" at the end would always force it: $ clang -target arm-elf-eabi -S mod.c -o - |

I am new to LLVM but have perused the code alongside using llvm-gcc and CLANG to build ARM EABI objects. Based on this superficial analysis it appears that LLVM currently does not support the ARM Exception Handling ABI (as defined under the EABI). Can anyone comment on whether plans are in place to remedy this? I did see the discussion regarding work on the MC for ARM. Will this work include

On Mon, Sep 27, 2010 at 8:50 AM, Dennis Taul <dtaul at codeaurora.org> wrote: > > I am new to LLVM but have perused the code alongside using llvm-gcc > and CLANG to build ARM EABI objects. > > Based on this superficial analysis it appears that LLVM currently does > not support the ARM Exception Handling ABI (as defined under the > EABI). > > Can anyone comment on