search for: crtstuff

...with -v gave me GNU C version 4.2.1 (Based on Apple Inc. build 5555) (LLVM build) (i686-pc-linux-gnu) compiled by GNU C version 4.2.1 (Ubuntu 4.2.1-5ubuntu4). so it seems to call the right compiler, but I still get /home/jo/llvm-gcc-wrk/./gcc/as --traditional-format -V -Qy -o crtbegin.o crtstuff.s GNU assembler version 2.18 (x86_64-linux-gnu) using BFD version (GNU Binutils for Ubuntu) 2.18 crtstuff.s: Assembler messages: crtstuff.s:15: Error: suffix or operands invalid for `push' crtstuff.s:29: Error: suffix or operands invalid for `call' crtstuff.s:36: Error: suffix or operands i...

On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 12:23 -0400 schrieb Daniel Berlin: >> To clarify, >> >> configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu >> --target=i686-pc-linux-gnu >> >> I do this all the time on my 4 core amd64 box and it works fine. > > There must be some other difference, as

Hello, I'm wondering why only some global static variables are marked with __used__ attributes in llvm-gcc/gcc/crtstuff.c. GCC compiles crtstuff.c with -fno-toplevel-reorder option, which ensures that unused static globals are not removed during optimization. However, since LLVM does not support that option, I presume __used__ attribute is used instead. For example, __CTOR_LIST__[1] definition is changed as follow...

Hello, > __used__ attributes in llvm-gcc/gcc/crtstuff.c. > GCC compiles crtstuff.c with -fno-toplevel-reorder option, which ensures > that > unused static globals are not removed during optimization. However, since > LLVM does not support that option, The problem is not that LLVM does not support this option. Though, this is indeed so due...

...4.2.1 (Based on Apple Inc. build 5555) (LLVM build) > (i686-pc-linux-gnu) > compiled by GNU C version 4.2.1 (Ubuntu 4.2.1-5ubuntu4). > > so it seems to call the right compiler, but I still get > > /home/jo/llvm-gcc-wrk/./gcc/as --traditional-format -V -Qy -o > crtbegin.o crtstuff.s > GNU assembler version 2.18 (x86_64-linux-gnu) using BFD version (GNU > Binutils for Ubuntu) 2.18 > crtstuff.s: Assembler messages: > crtstuff.s:15: Error: suffix or operands invalid for `push' > crtstuff.s:29: Error: suffix or operands invalid for `call' > crtstuff.s:3...

...so. My system compiler is GCC 4.1.1. >>> cc1: /usr/src/llvm/llvm/include/llvm/Target/TargetInstrInfo.h:151:const llvm::TargetInstrDescriptor& llvm::TargetInstrInfo::get(llvm::MachineOpCode) const: Assertion '(unsigned)Opcode < NumOpcodes' failed. /usr/src/llvm/llvm-gcc4/gcc/crtstuff.c: At top level: /usr/src/llvm/llvm-gcc4/gcc/crtstuff.c:314: internal compiler error: Aborted <<< This occurs only when building for Release. (Maybe I shouldn't do that with fresh CVS and SVN checkouts? :-) I'd build Debug, but I prefer sub-several-minute link times). If I switch...

...lloc-2.3.1/bin/.conf_check_79f1972132b1b06dc8dfdcac62686566/testbuild/default/testprog', '--cross-execute', 'arm-marvell-linux-gnueabi-gcc'] err: /home/balaram/MOXA/talloc-2.3.1/bin/.conf_check_79f1972132b1b06dc8dfdcac62686566/testbuild/default/testprog: In function `_fini': crtstuff.c:(.fini+0x0): multiple definition of `_fini' /home/balaram/MOXA/le/armv7_latest/bin/../arm-marvell-linux-gnueabi/libc/usr/lib/crti.o:(.fini+0x0): first defined here /home/balaram/MOXA/talloc-2.3.1/bin/.conf_check_79f1972132b1b06dc8dfdcac62686566/testbuild/default/testprog: In function `__data_...

...stem compiler is GCC 4.1.1. > > > cc1: /usr/src/llvm/llvm/include/llvm/Target/TargetInstrInfo.h:151:const llvm::TargetInstrDescriptor& llvm::TargetInstrInfo::get(llvm::MachineOpCode) const: Assertion '(unsigned)Opcode < NumOpcodes' failed. > /usr/src/llvm/llvm-gcc4/gcc/crtstuff.c: At top level: > /usr/src/llvm/llvm-gcc4/gcc/crtstuff.c:314: internal compiler error: Aborted > <<< > Hi Andrew, I too ran into this bug, which can be sidestepped by building LLVM with optimisation at the -O2 level (rather than the default -O3). My make command was: make E...

...-I../../gcc/../libcpp/include -I../../gcc/../libdecnumber -I../libdecnumber -I/home/regehr/llvm/include -I/home/regehr/llvm/include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer \ -c ../../gcc/crtstuff.c -DCRT_BEGIN \ -o crtbegin.o cc1: X86ATTAsmPrinter.cpp:543: void llvm::X86ATTAsmPrinter::printMemReference(const llvm::MachineInstr*, unsigned int, const char*): Assertion `isMem(MI, Op) && "Invalid memory reference!"' failed. ../../gcc/crtstuff.c:378: internal compile...

llvm-gcc 2.4 doesn't seem to compile; what is wrong? This is my first attempt to compile llvm-gcc. The llvm core compiled without problems. $ uname -a Linux ygramoel 2.6.26.5-45.fc9.x86_64 #1 SMP Sat Sep 20 03:23:12 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux $ gcc -v ... gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) $ svn co

.../gcc/../libdecnumber -I../libdecnumber -I/home/kooijman/src/llvm-trunk/include -I/home/kooijman/src/llvm-trunk/include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer \ -c ../../llvm-gcc-4.2-trunk/gcc/crtstuff.c -DCRT_BEGIN \ -o crtbegin.o In file included from /home/kooijman/src/llvm-gcc/obj/./gcc/include/limits.h:10, from ../../llvm-gcc-4.2-trunk/gcc/tsystem.h:108, from ../../llvm-gcc-4.2-trunk/gcc/crtstuff.c:68: /usr/include/limits.h:125:26: error: no include path in...

...bdecnumber -I/home/johan/llvm/obj/llvm/include -I/home/johan/llvm/src/llvm/include -m32 -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer -fno-asynchronous-unwind-tables \ -c ../../../src/llvm-gcc/gcc/crtstuff.c -DCRT_BEGIN \ -o 32/crtbegin.o In file included from /usr/include/features.h:359, from /usr/include/stdio.h:28, from ../../../src/llvm-gcc/gcc/tsystem.h:90, from ../../../src/llvm-gcc/gcc/crtstuff.c:68: /usr/include/gnu/stubs.h:7:27: error:...

...cts/llvm2.9/obj-llvm/include -I/home/dan/documents/projects/llvm2.9/llvm-2.9/include  -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer -fno-asynchronous-unwind-tables \  -c ../../llvm-gcc-4.2-2.9.source/gcc/crtstuff.c -DCRT_BEGIN \  -o crtbegin.o /tmp/ccWAqtEK.s: Assembler messages: /tmp/ccWAqtEK.s:36: Error: junk at end of line, first unrecognized character is `"' /tmp/ccWAqtEK.s:37: Error: bad expression /tmp/ccWAqtEK.s:37: Error: junk at end of line, first unrecognized character valued 0xffffffb0 m...

everyone-- I'm trying to build LLVM-GCC as a cross-compiler for a new target. I've successfully patched binutils, the FSF GCC, LLVM and Clang to build for this new target-- they work fine, but the LLVM-gcc build is failing for me. All my llvm.org sources are tracking the Subversion trunk, but my problem is probably not related to any ongoing churn there. I'm doing something

...libcpp/include -I/home/warren/llvm/llvm-2.0/include -I/home/warren/llvm/obj//include -m32 -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer -fno-asynchronous-unwind-tables -c ../../llvm-gcc4-2.0.source/gcc/crtstuff.c -DCRT_BEGIN -o 32/crtbegin.o Reading specs from /home/warren/llvm-gcc/obj/gcc/specs Target: x86_64-unknown-linux-gnu Configured with: ../llvm-gcc4-2.0.source/configure --prefix=/home/warren/llvm-gcc/obj../install --program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/ --enable-languages=c,c...

...ohan/llvm/obj/llvm/include -I/home/johan/llvm/src/llvm/include -m32 > -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions > -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer > -fno-asynchronous-unwind-tables \ > -c ../../../src/llvm-gcc/gcc/crtstuff.c -DCRT_BEGIN \ > -o 32/crtbegin.o > In file included from /usr/include/features.h:359, > from /usr/include/stdio.h:28, > from ../../../src/llvm-gcc/gcc/tsystem.h:90, > from ../../../src/llvm-gcc/gcc/crtstuff.c:68: > /usr/in...

陳韋任 wrote: > > Does your maching have directories like /lib64 and /usr/lib64? > Yes, it has /lib64 and /usr/lib64. > > > what is the size of a void pointer? > $ ./a.out > sizeof (void*) : 8 > > > Does this change if you add -m64 to the gcc command line? > No. Ok, as far as I cam tell, everything on your system is correct. I don't have any further ideas

...m/llvm-2.0/include -I/home/warren/llvm/obj//include > -m32 -g0 -finhibit-size-directive -fno-inline-functions -fno- > exceptions > -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame- > pointer > -fno-asynchronous-unwind-tables -c > ../../llvm-gcc4-2.0.source/gcc/crtstuff.c -DCRT_BEGIN -o 32/ > crtbegin.o > Reading specs from /home/warren/llvm-gcc/obj/gcc/specs > Target: x86_64-unknown-linux-gnu > Configured with: ../llvm-gcc4-2.0.source/configure > --prefix=/home/warren/llvm-gcc/obj../install --program-prefix=llvm- > --enable-llvm=/home/warren/...

.... There are instructions like this one "lis 30, ha16(completed.5554.b)" which are not understood apparently? Should this instruction be understood by the assembler? Thanks, Maarten -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: crtstuff.s URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110518/7b4ce619/attachment.ksh>

...lvm/llvm-1.9/include -I/h ome/ferad/llvm/llvm-obj/include -m32 -g0 -finhibit-size-directive -fno-inline-fu nctions -fno-exceptions -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-om it-frame-pointer -fno-asynchronous-unwind-tables \ -c ../../llvm-gcc-src/gcc/crtstuff.c -DCRT_BEGIN \ -o 32/crtbegin.o Warning: Generation of 64-bit code for a 32-bit processor requested. In file included from ../../llvm-gcc-src/gcc/crtstuff.c:67: ../../llvm-gcc-src/gcc/unwind-dw2-fde.h: In function âget_cieâ: ../../llvm-gcc-src/gcc/unwind-dw2-fde.h:163: warning: return from...