similar to: [LLVMdev] Mips patches for LLVM 3.5.2

Klibc FTBFS with '-mno-odd-spreg' on mips32(el) platforms, As it try to save/restore odd-number FPR. Indeed no other architectures save/restore FPR at all. It shouldn't be needed. --- usr/klibc/arch/mips/setjmp.S | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/usr/klibc/arch/mips/setjmp.S b/usr/klibc/arch/mips/setjmp.S index 68eed19..21e4115 100644 ---

On 06/16/2015 06:21 PM, Daniel Sanders wrote: > > > > the best I can suggest is to target mips2 and O32 > > > > It's not work for all, still get Assembler messages error on some > source files > > > > > Warning: float register should be even, was 7 > > Could you add –save-temps to the compiler command and send me the > command along with the

Hi all, On behalf of Andes Technology Corp, I am proposing a backend targeting the NDS32 V3 ISA. NDS32 V3 ISA is a 16/32 bit mixed instruction set architecture that developed By AndesTech. You can find more information at the Andes website <http://www.andestech.com/>, and reference AndeStar ISA Manual (V3 ISA) from document download page <http://www.andestech.com/product.php?cls=9>.

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

Any idea about it? It may be a serious problem, as some distributions are using FPXX by default. On Sat, Sep 5, 2015 at 9:39 PM, YunQiang Su <wzssyqa at gmail.com> wrote: > Klibc FTBFS with '-mno-odd-spreg' on mips32(el) platforms, > As it try to save/restore odd-number FPR. > > Indeed no other architectures save/restore FPR at all. > It shouldn't be needed. >

Hi, I have a llvm asssembly version of radix_mod.c modified from radix (a splash2 bench mark). It is named radix.bc. I have extended the number of arguments from 2 to 4 in the function called product_mod_46 and saved it as a new file called radix_mod.bc . Although the extra arguments does not do anything in the function. It still broke the code on sparc. However, both versions of the byte code

ckathy wrote: > > Hi, > > I have a llvm asssembly version of radix_mod.c modified from radix (a > splash2 bench mark). It is named radix.bc. > > I have extended the number of arguments from 2 to 4 in the function called > product_mod_46 and saved it as a new file called radix_mod.bc . Although > the extra arguments does not do anything in the function. It still broke

> > I assume with target you mean the backend? Consider the x86 backend. It > supports 32bit and 64bit mode, with the GNU x32 ABI in between. There > are three different executable formats support (ELF, PE, MachO) with > different constraints. Some platforms require 32bit alignment of the > stack, others require 128bit alignment. The list goes on. The triple > specifies >

Hi Daniel, attached is a patch that pushes most of the object file specific parsing out of AsmParser and down into MachOAsmParser. This was done as a cleanup for the ELF work. I know that you're not happy with this approach, particularly the fact that as we add more object file formats and assembler dialects, it's going to cause a class explosion. But I was hoping that we could use this