search for: mips4

...to remove it. For example, if I specify -march=armv7-a, it *shouldn't* need me to put "-target arm" before it to work! One thing that I've been pondering for a little while is making clang's use of the triple a config file. In particular, we'd like to invoke things like mips4-unknown-freebsd-clang and have it really mean 'clang -target mips64-unknown-freebsd -mcpu=mips4 -msoft-float --sysroot=/usr/local/sysroots/mips4 {whatever}'. For cross compiles, we'd only need one clang, a symlink, and a config file. I pondered a more structured config file, but reall...

Full_Name: George N. White III Version: 1.9.0 OS: Irix 6.5.21m Submission from: (NULL) (142.176.61.212) R-1.9.0 built using the SGI MIPSPro compilers Installation directory: /usr/local C compiler: c99 -OPT:IEEE_NaN_inf=ON -mips4 -n32 -O3 -OPT:Olimit_opt=on C++ compiler: CC -OPT:IEEE_NaN_inf=ON -mips4 -n32 -O3 -OPT:Olimit_opt=on -LANG:std Fortran compiler: f90 -OPT:IEEE_NaN_inf=ON -mips4 -n32 -O3 -OPT:Olimit_opt=on Interfaces supported: X11, gnome, tcltk External libraries: readlin...

...have to kill the entire window and start the window and connection all over again. This is completely repeatable. I get this error if I resize the window quickly several times. I have X Windows forwarding on. Below is the line I use to configure OpenSSH: configure --with-cflags="-n32 -mips4 -O3 -r10000 -TARG:processor=r10000:platform=ip28 -I/usr/local/include" --with-ldflags="-n32 -mips4 -L/usr/local/lib -Wl,-s,-x -Wl,-rpath,/usr/local/lib" --prefix=/usr/local --with-tcp-wrappers --with-prngd-socket=/var/adm/entropy --with-ssl-dir=/usr/local/lib --with-catman=man --mand...

...uname -aR = IRIX64 mendel 6.5 6.5.16f 04101930 IP35 We built R on an SGI system using the following configure script: # explicitly choose vendor compilers for R rather than GNU # optimise output to support highest level of performance for the processors on OCGC export CC="/usr/bin/cc -n32 -mips4 -r12000" export CXX="/usr/bin/CC -n32 -mips4 -r12000" export F77="/usr/bin/f77 -n32 -mips4 -r12000" # these flags appear to be necessary to build with tcl/tk export TCLTK_LIBS='-L/usr/local/lib32' export TCLTK_CPPFLAGS='-I/usr/local/include/tcl -I/usr/local/incl...

The term "target" is somewhat overloaded. When llvm-config tells you it was built with the X86 target, that actually includes a variety of closely related architectures, such as x86_64, i386, and so on. Within the x86_64 architecture, there are many individual processor implementations that LLVM understands, such as Skylake, Bulldozer, and many many more. What *clang* means by

Hi Tim, 2014-06-25 15:26 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > Hi Kevin, > > I assume you've looked at the GCC documentation in this area, since > your ideas are very similar: > https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html. I actually > think that looks like a rational set of conventions too. > > The main difference appears to be

...tvector.o printutils.o random.o RNG.o regex.o relop.o saveload.o scan.o seq.o sort.o source.o split.o subassign.o subscript.o subset.o summary.o unique.o util.o version.o xxxpr.o ../unix/libunix.a ../appl/libappl.a ../nmath/libmath.a -lSM -lICE -lX11 -lblas -LNO:plower=off -LANG:=f77 -L/usr/lib64/mips4 -L/usr/lib64 -lftn -lm -ltermcap -lm ld64: WARNING 84: /usr/lib64/libSM.so is not used for resolving any symbol. ld64: WARNING 85: definition of main in ../unix/libunix.a(system.o) preempts that definition in /usr/lib64/mips4/libftn.so. ld64: WARNING 84: /usr/lib64/libtermcap.so is not used for r...

I have a zip file. It is over 2Gb in size: -rw-r--r-- 1 sweh sweh 2383956582 Mar 13 13:44 test.zip The standard "unzip" program barfs: % unzip -l test.zip Archive: test.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment

...d in this project : > > I have a PlayStation Portable and like to develop several projects using > all of its potential. > > PSP has two Allegrex cpus : SC (system control) and ME (Media Engine). > Both are designed with a MIPS 2 core plus a dozen instructions borrowed from > MIPS4. > Both also have a standard FPU coprocessor. > But only SC processor has a second coprocessor called VFPU which allows > matrix and vector computations. > > Actually, gcc doesn't handle VFPU at all (i'm speaking about the compiler, > not the assembler). > > I tri...

My guess is he wants mips1 so that he doesn't have to worry about the patented mips instructions? At any rate, it will be a bit of work to enable a mips1 target and I doubt many people are interested, so it'll definitely be up to him to do the work. -eric On Fri, Apr 26, 2013 at 10:15 AM, Reed Kotler <rkotler at mips.com> wrote: > If you want to create a version for the mips1

I'm cross-compiling for MIPS. The test-case is as simple as it can be: void foo() {} $clang -target mips64-octeon-linux -c -B path/to/cross/compiled/mips/assembler a.c And then I look at the object file: $ nm a.o 0000000000000020 t $tmp0 0000000000000000 T foo I would like to know what "$tmp0" is. Furthermore, if I pass -g to clang, I see a whole bunch of such symbols. Some of

...e no idea and this is why I’m asking. Now Clang accepts the following MIPS CPU names. This list can be found in the "clang/lib/Basic/Targets/Mips.cpp". mips1 and mips5 accepted by Clang, but unsupported by code generator. I'm going to remove them from this list. mips1, mips2, mips3, mips4, mips5, mips32, mips32r2, mips32r3, mips32r5, mips32r6, mips64, mips64r2, mips64r3, mips64r5, mips64r6, octeon, octeon+, p5600 R3000 is a CPU implements mips1 instruction set architecture. Unfortunately you cannot generate a code for this CPU using Clang. -- Simon Atanasyan Als GmbH eingetragen i...

...rver: Intel PIII 550MHz running Gentoo Linux with Kernel 2.6.23.1 (vanilla sources). fuse 2.7.0, glusterfs-1.3.11 (client+server). Laptop: Intel PII 300MHz running Gentoo Linux with Kernel 2.6.25 (vanilla sources). fuse 2.7.0, glusterfs-1.3.11 (client+server) Cobalt Qube2: QED RM5231 250MHz (MIPS4 Little Endian) running Gentoo Linux with kernel 2.6.27-rc4 (latest linux-mips.org git sources). glusterfs-1.3.11 (server only for now, but will be installing fuse and the client soon). All boxes are synced to the local NTP server which runs at Stratum 2. Other machines to be added into the mix:...

...riple mipsel-linux-gnu' means? You're probably thinking something like "mips32r2 little endian, obviously" but this is not actually correct all the time. The true answer is 'whatever I (the person who built the toolchain) want it to mean'. It could be mips32r6, it could be mips4, it could even be big-endian mips64r5 with nan2008 and msa. It could even be octeon or p5600. In GCC toolchains, distributors routinely use configure-time options to define the triple they wish to use. Nothing is stopping anyone using the same string for completely different meanings and indeed con...

I think we need to take a step further back and re-enter from the right starting point. The thing that's bothering me about the push back so far is that it's trying to discuss and understand the consequences of resolving the core problem while seemingly ignoring the core problem itself. The reason I've been steering everything back to GNU Triple's being ambiguous and inconsistent