search for: o32

...at there seem to be incompatible extensions to some of these ABI's too. :) > >> I'm pretty sure Imagination Technologies working up a new abi right now. > > Not exactly. We're not working on any completely new ABI's but we are fixing a compatibility flaw between the O32 ABI and a (currently) unsupported extension that allows the efficient use of FR=1 mode (FPU with 64-bit registers). This is going to be important since MIPS32r6/MIPS64r6 will not have direct support for FR=0 mode (FPU with 32-bit registers). At the moment, this extension is available in all the too...

> So in summary, each step is ABI compatible with the previous step. The linker will ensure that the end-user doesn't try to do the second step before the first step is finished since it will refuse to link a binary that contains both O32 and O32+fp64. It will produce an O32 binary given a combination of O32+fpxx, and similarly a O32+fp64 binary given a combination O32+fpxx and O32+fp64. > Interesting. I'd seen some of the discussion, but not read it in any detail. >> Curious why an extension to o32 for this and not,...

On 06/12/2015 07:12 PM, Daniel Sanders wrote: > > Hi, > > I'm afraid targeting a 64-bit CPU and the O32 ABI is completely broken > at the moment, it's one of the very long-standing issues I'm working > towards. The main problem is that a lot of the internals of the Mips > LLVM backend derive their behaviour from the target CPU rather than > the target ABI. In theory, the combi...

...arameters llvm/configure \ --prefix=/usr \ --target=mipsel-unknown-linux-gnu \ --enable-targets=mips \ --enable-optimized \ --enable-shared \ --disable-assertions I want to build code for *mips3* with *o32* abi, but fails: mipsel-unknown-linux-gnu-clang++ test.cpp -mips3 /tmp/test-a51985.s: Assembler messages: /tmp/test-a51985.s:11: Warning: `fp=64' used with a 32-bit ABI /usr/local/bin/mipsel-unknown-linux-gnu-ld: Warning: a.out uses -mdouble-float (set by /opt/toolchain_clang/host/usr/mipsel-u...

...re implemented a long time ago and I can only guess at this point but I'd say that there were some misinterpretations of the spec and given the popularity of GCC, the implementation became the new standard and it's something that LLVM needs to cope with. > There are a lot of MIPS ABIs. o32, n32, n64 - These came from the SGI world for IRIX originally, but were also adopted for linux and used in gcc for both. o64 - Invented at Cygnus for 64-bit processors eabi - Different one invented at Cygnus meabi - Invented with MIPS and Cygnus (and possibly others) in the late 90s as a new embedd...

I get this error: cc -o32 -g -I/usr/local/include -I/var/tmp/openssl-o32/include -I/var/tmp/openssl-o32/include -I. -I./openbsd-compat -I. -DETCDIR=\"/usr/local/ssh/etc\" -D_PATH_SSH_PROGRAM=\"/usr/local/ssh/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/local/ssh/libexec/ssh-askpass\" -D_PATH_SF...

But then I should write // CHECK: something // SSE: something // SSE3: something With this feature it can be write // {{[A-Z0-9]+}} : something From: James Y Knight [mailto:jyknight at google.com] Sent: Thursday, May 26, 2016 5:53 PM To: Ehsan Amiri <ehsanamiri at gmail.com> Cc: Elena Lepilkina <Elena.Lepilkina at synopsys.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject:

On Thu, May 26, 2016 at 10:35 AM, Ehsan Amiri via llvm-dev < llvm-dev at lists.llvm.org> wrote: > 7. Wildcard for prefixes - If some statements should be checked > regardless prefix, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME > and etc. > >> 8. Prefix with regular expressions - If statement should be >> checked if prefix matches some regular

...ddir':"llvm-mips-linux", 'factory': LLVMBuilder.getLLVMBuildFactory("mips-linux-gnu", timeout=40, config_name='Release+Asserts', extra_configure_args=["--with-extra-options=-mips32r2", + "CC=/mips/proj/build-compiler/clang-be-o32-r203581/bin/clang", + "CXX=/mips/proj/build-compiler/clang-be-o32-r203581/bin/clang++", "--with-extra-ld-options=-mips32r2"])}, {'name': "llvm-aarch64-linux", 'slavenames':["aarch64-foundation"],

...on available is the triple which I know to be unreliable. For example, our backend currently considers mips64-linux-gnu to be a 64-bit architecture using the N64 ABI. This is a problem because having a 64-bit CPU does not require the ABI to be N64 or even 64-bit (N32/N64). It's valid to produce O32 code for a 64-bit processor (and triple) and many of my test systems (e.g. 32-bit Debian on a MIPS64R2 processor) actually need this since the host triple detected by config.guess is mips64-linux-gnu. As things stand, attempting to emit O32 code on a mips64-linux-gnu host crashes the compiler unles...

https://bugzilla.mindrot.org/show_bug.cgi?id=2590 Bug ID: 2590 Summary: Seccomp filter for missing architectures Product: Portable OpenSSH Version: 7.2p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority: P5 Component: sshd

...gards, Yu Rong Tan On Mon, Jun 16, 2014 at 5:30 PM, Matheus Almeida <Matheus.Almeida at imgtec.com> wrote: > Could you be more specific about what ABIs are you after ? The reason I'm asking is that there are several ABIs available for Mips and only a few of them are supported by LLVM (o32, n32 and n64). There are several ABIs defined by GNU with very little documentation that describes them (EABI is one example). > > We are aware that the available documentation and GCC disagree sometimes and given that GCC is the de-facto standard, LLVM tries to follow GCC's behaviour as...

Here are some examples using the gnu assembler reacting to the same input file with different commandline options. These are using the GCC assembler on hello.c // abi o32, arch mips32r2, relocation model pic+cpic mips-linux-gnu-as -mips32r2 -EL -KPIC -o hello_gas.o hello_gas.s e_flags 0x70001007 EF_MIPS_NOREORDER EF_MIPS_PIC EF_MIPS_CPIC E_MIPS_ABI_O32 EF_MIPS_ARCH_32R2 // abi o32, arch mips32r2, relocation model cpic mips-linux-gnu-as -mips32r2 -EL...

Hi folks,. I'm working on a project on Irix 6.3 using CC (not GCC) and the .o32 object format (not n32) and would like to incorperate ogg-vorbis. Is there any way to configure the libogg/libvorbis makefiles to work with CC? (Or does anyone know how to arm-twist GCC under Irix 6.3 into producing o32 object files?) Thanks super-much for any help, Mike <p>--- >8...

On Dec 10, 2012, at 1:15 PM, "Carter, Jack" <jcarter at mips.com> wrote: > Here are some examples using the gnu assembler reacting to the same input file with different commandline options. > > These are using the GCC assembler on hello.c > // abi o32, arch mips32r2, relocation model pic+cpic > mips-linux-gnu-as -mips32r2 -EL -KPIC -o hello_gas.o hello_gas.s > e_flags 0x70001007 EF_MIPS_NOREORDER EF_MIPS_PIC EF_MIPS_CPIC E_MIPS_ABI_O32 EF_MIPS_ARCH_32R2 > > // abi o32, arch mips32r2, relocation model cpic > mips-l...

Hello, I have just compiled openssh version 2.1.0p2 n irix 6.5.5 an encounterd the following 'problem'. On IRIX there are 3 abi's (Application Binary Interface). o32) The old 32-bit ABI which was standard on IRIX 5 systems n64) The 64-bit ABI n32) The new high performance 32-bit ABI On IRIX the libraries are installed as follows: /usr/lib) For the o32 libraries /usr/lib32) For the n32 libraries (is usual the default) /usr/lib64) For...

...have specified? It doesn't reflect the effects of the command line options but the backend believes it does. It also conflates having a mips64 architecture with intending to use a mips64 architecture but these aren't quite the same thing. For example, 'mips-linux-gnu –mips64' means O32 on a MIPS64 which is effectively MIPS32 and O32 in terms of what the compiler is permitted to use. This is the main reason I want to separate the textual llvm::Triple from the understanding of what the llvm::Triple means. I want to be able to take an initial meaning and mutate it according to the o...

...one ABI selected. > > There was a lot of code (some of which didn't have access to target features) in the backend that tried to derive the ABI from the arch component of the triple (e.g. mips64 => n64 ABI) even though there were multiple possible ABI's for each arch (mips64 => o32, n32, or n64 ABI's) and there isn't a canonical choice for any given triple (it varies between linux distributions and toolchains in general). Settling on -target-abi allowed us to sort out the inconsistencies in the backends opinion of what the selected ABI was. It also allowed us to move...

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 .i and .s file...

...et>ELFObjectWriter On Dec 10, 2012, at 1:15 PM, "Carter, Jack" <jcarter at mips.com> wrote: > Here are some examples using the gnu assembler reacting to the same input file with different commandline options. > > These are using the GCC assembler on hello.c > // abi o32, arch mips32r2, relocation model pic+cpic > mips-linux-gnu-as -mips32r2 -EL -KPIC -o hello_gas.o hello_gas.s > e_flags 0x70001007 EF_MIPS_NOREORDER EF_MIPS_PIC EF_MIPS_CPIC E_MIPS_ABI_O32 EF_MIPS_ARCH_32R2 > > // abi o32, arch mips32r2, relocation model cpic > mips-linu...