search for: fkeep

...d be lowered to a new invariant TargetOpcode (e.g. FAKE_USE), which serves the same purpose at the MI level. Code emission would simply ignore the new opcode. Frontends could use the intrinsic to extend liveranges of variables as desired. As a first use case, clang would accept a new option (e.g. -fkeep-this-ptr) which would cause a fake use of 'this' to be inserted at the end of a function, making it available for inspection throughout the entire function body. One important note is that since such an option would affect code generation, it cannot be automatically enabled by -g. However,...

...-collect2, unless you pass -enable-ld to it, in which case it will call llvm-ld, and link the bc files. To build an average app into bc files: 1) configure with standard llvm-gcc (don't pass -enable-ld to llvm-gcc) 2) build with something like: make CC=llvm-gcc CFLAGS+='-emit-llvm -g -O0 -fkeep-inline-functions -fno-inline -finline-limit=0 -Wl,-enable-ld -Wl,-O0 -Wl,-disable-inlining -Wl,-disable-opt' To get the make line right, you will need to know the details of your build process, if it relies on LD and LDFLAGS, use something like: make CC=llvm-gcc LD=llvm-ld CFLAGS+='-g -I....

...(e.g. > FAKE_USE), which serves the same purpose at the MI level. > > Code emission would simply ignore the new opcode. > > > Frontends could use the intrinsic to extend liveranges of variables as > desired. As a first use case, clang would accept a new option > > (e.g. -fkeep-this-ptr) which would cause a fake use of 'this' to be > inserted at the end of a function, making it available for inspection > > throughout the entire function body. > Do you have much in the way of performance numbers to get a sense of the impact of this feature? (& poss...

...ty/llvm.ia64/llvm-gcc4.2-2.1.source/configure --prefix=/liberty/llvm.ia64/install --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ --disable-shared The build of llvm seems to succeed, but llvm-gcc dies with the following messages: gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -I. -I. -I/liberty/llvm.ia64/llvm-gcc4.2-2.1.source/gcc -I/liberty/llvm.ia64/l...

...nfigure > --prefix=/liberty/llvm.ia64/install > --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ > --disable-shared > > The build of llvm seems to succeed, but llvm-gcc dies with the following > messages: > > gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions > -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes > -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros > -Wold-style-definition -Wmissing-format-attribute -fno-common > -DHAVE_CONFIG_H -I. -I. -I/liberty/llvm.ia64/llvm-gcc4.2-2.1.source/gcc &g...

...d be lowered to a new invariant TargetOpcode (e.g. FAKE_USE), which serves the same purpose at the MI level. Code emission would simply ignore the new opcode. Frontends could use the intrinsic to extend liveranges of variables as desired. As a first use case, clang would accept a new option (e.g. -fkeep-this-ptr) which would cause a fake use of 'this' to be inserted at the end of a function, making it available for inspection throughout the entire function body. One important note is that since such an option would affect code generation, it cannot be automatically enabled by -g. However,...

....ia64/install >> --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ >> --disable-shared >> >> The build of llvm seems to succeed, but llvm-gcc dies with the >> following >> messages: >> >> gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions >> -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes >> -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros >> -Wold-style-definition -Wmissing-format-attribute -fno-common >> -DHAVE_CONFIG_H -I. -I. -I/liberty/llvm.ia64/llvm-gcc4.2-2.1.so...

...align-jumps-max-skip -falign-loops # -falign-loops-max-skip -fargument-alias -fbranch-count-reg -fcommon # -fearly-inlining -feliminate-unused-debug-types -femit-class-debug-always # -fexceptions -ffunction-cse -fgcse-lm -fglobal-alloc-prefer-bytes -fident # -finline-functions-called-once -fivopts -fkeep-static-consts # -fleading-underscore -flocal-alloc -fmove-loop-invariants -fpeephole # -freg-struct-return -fsched-interblock -fsched-spec # -fsched-stalled-insns-dep -fshow-column -fsplit-ivs-in-unroller # -ftoplevel-reorder -ftree-loop-im -ftree-loop-ivcanon # -ftree-loop-optimize -ftree-vect-loo...

> LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. I am trying with llvm-gcc-4.2 from svn. Aaron

...ty/llvm.ia64/llvm-gcc4.2-2.1.source/configure --prefix=/liberty/llvm.ia64/install --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ --disable-shared The build of llvm seems to succeed, but llvm-gcc dies with the following messages: gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -I. -I. -I/liberty/llvm.ia64/llvm-gcc4.2-2.1.source/gcc -I/liberty/llvm.ia64/l...

...es/745/srcs/llvm-gcc/obj/gcc/../../llvm-gcc4.2-2.1.source/gcc /toplev.c:637: multiple definition of `_exact_log2' llvm-main.o:/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/stl_algob ase.h:(.text$exact_log2[_exact_log2]+0x0): first defined here ------- the actual command line is: c++ -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o cc1-dummy.exe c-lang.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c...

...ble-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ >>> --disable-shared >>> >>> The build of llvm seems to succeed, but llvm-gcc dies with the >>> following >>> messages: >>> >>> gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions >>> -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes >>> -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros >>> -Wold-style-definition -Wmissing-format-attribute -fno-common >>> -DHAVE_CONFIG_H -I. -I. -I/liberty/llvm.ia64/ll...

...4/llvm-2.1/ --enable-languages=c,c++ >>>> --disable-shared >>>> >>>> The build of llvm seems to succeed, but llvm-gcc dies with the >>>> following >>>> messages: >>>> >>>> gcc -Wall -c -DUSE_LIBUNWIND_EXCEPTIONS -g -fkeep-inline-functions >>>> -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes >>>> -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros >>>> -Wold-style-definition -Wmissing-format-attribute -fno-common >>>> -DHAVE_CONFIG_H -I. -I. -I/libe...

...nline and static, if all calls to the function are integrated into the caller, and the function's address is never used, then the function's own assembler code is never referenced. In this case, GNU CC does not actually output assembler code for the function, unless you specify the option `-fkeep-inline-functions'. Some calls cannot be integrated for various reasons (in particular, calls that precede the function's definition cannot be integrated, and neither can recursive calls within the definition). If there is a nonintegrated call, then the function is compiled to assembler code...