similar to: [LLVMdev] cross compiling with the C backend

On Wed, Feb 27, 2008 at 7:32 PM, Mike Stump <mrs at apple.com> wrote: > On Feb 27, 2008, at 8:38 AM, HyperQuantum wrote: > > I tried to cross-compile llvm-gcc for mips, but it crashes > > But now I'm stuck. I don't need a full cross-compiler, just generating > > LLVM code is sufficient for me. > > make -k install will install a mips cross compiler for

On Feb 19, 2008 5:24 PM, Anton Korobeynikov <asl at math.spbu.ru> wrote: > > Could you give an example? > Different alignment issues, for example. LLVM handles alignment > explicitely by inserting dummy padding fields. Surely, the stuff can be > different for build platform and for target one. > > Also, many platform-dependent stuff in POSIX-aware code (see example

For my master's thesis, I am trying to cross compile programs for the PSP (PlayStation Portable) with LLVM and llvm-gcc. This is what I do: (1) compile a program and the libraries it uses (libpng etc.) with llvm-gcc (2) link the bitcode files with llvm-ld into one file (3) run "llc -march=c" on the result (4) compile the resulting C source with the PSP toolchain It seems to work

Kevin André wrote: > For my master's thesis, I am trying to cross compile programs for the > PSP (PlayStation Portable) with LLVM and llvm-gcc. > > This is what I do: > > (1) compile a program and the libraries it uses (libpng etc.) with llvm-gcc > (2) link the bitcode files with llvm-ld into one file > (3) run "llc -march=c" on the result > (4) compile

On Feb 27, 2008, at 8:38 AM, HyperQuantum wrote: > I tried to cross-compile llvm-gcc for mips, but it crashes > But now I'm stuck. I don't need a full cross-compiler, just generating > LLVM code is sufficient for me. make -k install will install a mips cross compiler for you, I believe. If you don't want to install it, you can run it as cd gcc && ./xgcc - B./ t.c.

From: Michael Davidson <md at google.com> Add cc-name to klibc/scripts/Kbuild.include. Make optimization flags not supported by clang conditional on cc-name. Don't use -nostdinc when building klibc. While klibc doesn't (shouldn't) use the standard header files supplied by the toolchain, it does still need to be able to find the compiler-specific header file

On Feb 28, 2008, at 4:03 AM, HyperQuantum wrote: > /home/kevin/Documents/School/Thesis/work/install/llvmgcc-mips/bin/ > llvm-gcc > -nostdlib -nostdinc > -I/home/kevin/Documents/School/Thesis/work/install/psptoolchain/psp/ > include > -I/home/kevin/Documents/School/Thesis/work/install/psptoolchain/lib/ > gcc/psp/4.1.0/include > -c -emit-llvm -Wall \ >

I tried to cross-compile llvm-gcc for mips, but it crashes somewhere in the build process: /home/kevin/Documents/School/2eLIC/Thesis/work/build/llvmgcc-mips/./gcc/xgcc -B/home/kevin/Documents/School/2eLIC/Thesis/work/build/llvmgcc-mips/./gcc/ -B/home/kevin/Documents/School/2eLIC/Thesis/work/build/llvmgcc-mips/../../install/llvmgcc-mips/mips-unknown-linux-gnu/bin/

Somehow I wish not all parts of a libc but parts that can be provided without a JavaScript wrapper for .wasm can be provided from llvm's libc (leaving a stab implementation for the rest like file system). I've put together a minimal libc on [1] so using a 26kb .wasm binary file one can decode both PNG and JPG using this [2] simple to integrate JavaScript code, can be easily ported in other

Hello, Kevin > build process I described in my original message. So the difference is > more subtle; maybe a difference in the layout of structs or something. Also, there can be another ABI differences. > llvmoutput.c:17976: warning: pointer targets in passing argument 1 of > 'longjmp' differ in signedness Hrm, are you using setjmp/longjmp stuff? They're definitely not

On Fri, Mar 7, 2008 at 8:28 PM, Bruno Cardoso Lopes <bruno.cardoso at gmail.com> wrote: > When using mips-unknown-linux-gnu as a cross-compiler, the llvm Mips > backend is called by cc1 and with that you get llvm bytecode defined > relative to the Mips ABI. That was my intention. The PSP has a 32-bit MIPS (derived) CPU. What I don't know is if that triple is the right one

This is a series of patches for clang compatibility: - Using flags needed flags and removing unsupported flags. - Adding support for clang's LLD linker. - Removing a variety of warnings. Bill Wendling (3): [klibc] Kbuild: use "libc.a" with clang [klibc] Kbuild: Add "-fcommon" for clang builds [klibc] Clean up clang warnings Michael Davidson (1): [klibc] Kbuild:

When we add -ffreestanding the compiler won't get to inline this any more. Signed-off-by: David Woodhouse <dwmw2 at infradead.org> --- com32/lib/math/fabs.S | 15 +++++++++++++++ mk/lib.mk | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) create mode 100644 com32/lib/math/fabs.S diff --git a/com32/lib/math/fabs.S b/com32/lib/math/fabs.S new file mode 100644 index

For compiling the xen kernel we use -nostdinc which means we don''t want to rely on any external headers. That also counts vor stdarg.h. Use the external header when we compile the tools. Adapt libelf-loader.c which is compiled in the kernel and with the tools. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced

- UPS MGE Premium Ellipse Premium 1200 - SuSE Linux 10.0 OSS, kernel 2.6.13 smp - gcc version 4.0.2 20050901 (prerelease), glibc-2.3.5-40 - mgeups-psp-3.0.0-3, nut-2.0.2-4 - Dell Dimension 8400 with dual core Intel Xeon. 3.0GHz. lsusb shows: Bus 002 Device 003: ID 0463:ffff MGE UPS Systems UPS less /proc/bus/usb/devices shows for bus 2 device 3: T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=

Hi. : ) I was updating my unofficial Korean Ogg Vorbis FAQ, when I noticed the following: While #ext is no longer listed in the FAQ contents, http://www.vorbis.com/faq.psp#ext still exists. IMHO http://www.vorbis.com/faq.psp#stream looks a little awkward. I suggest something like: Icecast streams Ogg vorbis to playsers like XMMS, Winamp 2, and foobar2000, which are all capable of...

16396:055d98aa2dd0 almost works but not quite. LDFLAGS_DIRECT means we end up with: gld -melf_i386 -nostdlib -N -Ttext 0x100000 -o hvmloader.tmp hvmloader.o mp_tables.o util.o smbios.o 32bitbios_support.o acpi/acpi.a Specifying a linker script and asking for -nostdlib is obviously contradictory. Removing $(LDFLAGS_DIRECT) fixes the problem. regards john

On Fri, 2020-03-27 at 15:29 -0700, Bill Wendling wrote: > From: Michael Davidson <md at google.com> > > Add cc-name to klibc/scripts/Kbuild.include. [...] > --- a/scripts/Kbuild.klibc > +++ b/scripts/Kbuild.klibc > @@ -107,8 +107,15 @@ KLIBCOBJCOPY := $(OBJCOPY) > KLIBCOBJDUMP := $(OBJDUMP) > > # klibc include paths > -KLIBCCPPFLAGS := -nostdinc

Dear List, I thought it might be useful if I wrote up my notes on getting an MGE UPS to work with NUT and openSUSE. The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE 10.2, but not "out-of-the-box": there are some things you need to do: Intro. MGE have built rpms of NUT which greatly simplify installation. Merci MGE. I used the rpm's for nut-2.0.5 and the

On Mar 18, 2008, at 10:46 PM, Bruno Cardoso Lopes wrote: > Hi all, > > Last year i was mentored by Chris Lattner at GSoC and i created the > Mips back-end for LLVM. The back-end is still experimental (working > with simple benchmarks only) and this year i would like to improve it > as my GSoC proposal. Mips is still fairly used nowadays in a lot of > devices - routers,