similar to: [LLVMdev] #line in generated C code

Do you have a verify option in your loaded module? Reid. On Sun, 2006-08-20 at 22:04 +0200, Bram Adams wrote: > Hi, > > Op 20-aug-06, om 21:18 heeft Reid Spencer het volgende geschreven: > > > I looked over your patch and it looks good. I applied a patch based on > > yours. The llvm-ld tool now uses the PluginLoader just like the opt > > tool. It will also run

Hi Bram, Could you submit bug reports for all of these problems? Thanks! -bw On 5/29/07, Bram Adams <bram.adams at ugent.be> wrote: > Hi, > > Today I managed to link ioquake3, but generating a binary does not > work yet. > > > 1) On OSX, I get: > > Error: Code generator does not support intrinsic function > 'llvm.ppc.altivec.lvsl'! > > when I

Hi Bram, On Fri, 2007-05-18 at 18:12 +0200, Bram Adams wrote: > Hi, > > Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven: > > >> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build > >> with the header files using uintptr_t (not recognised as a type). > >> Putting "#include <stdint.h>" in

Yeah, it wasn't your problem but mine. Please update Optimize.cpp or apply the recent patches to it. Should be fixed now. Reid. On Sun, 2006-08-20 at 22:59 +0200, Bram Adams wrote: > Hi, > > Op 20-aug-06, om 22:26 heeft Reid Spencer het volgende geschreven: > > > Do you have a verify option in your loaded module? > > What exactly do you mean by "verify

On Wed, 9 Jul 2008, Bram Adams wrote: > Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt > with two dynamic libraries to "-load", the first of which contains > transformation passes and support code whereas the second one provides > extra passes which make use of the first library's support code. In > other words, the symbols loaded in for the

Hi, There is a typo in $LLVM_SRC/Makefile.rules on line 750 where it says : SharedLibKindMessage := "Lodable Module" instead of SharedLibKindMessage := "Loadable Module" Op 15-nov-06, om 15:54 heeft Bram Adams het volgende geschreven: > Didn't check > LLVM's test suite. Doing the simple LLVM-tests (on Slackware 10.2) gets: === Summary ===

Hi, Op 20-aug-06, om 22:26 heeft Reid Spencer het volgende geschreven: > Do you have a verify option in your loaded module? What exactly do you mean by "verify option"? Anyway, I did a grep on "verify" in my code, but found nothing. Kind regards, Bram Adams GH-SEL, INTEC, Ghent University (Belgium)

Hi, Op 15-nov-06, om 03:26 heeft Tanya M. Lattner het volgende geschreven: > I'm able to reproduce this if I skip doing a "make" and directly do a > "make install" after configuring. I believe we require people to do > a full > build before attempting to install. So I don't think its really a bug. > Could you try doing a make first and then install?

Hi, Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt with two dynamic libraries to "-load", the first of which contains transformation passes and support code whereas the second one provides extra passes which make use of the first library's support code. In other words, the symbols loaded in for the first library should be available when the second

Hi, Op 20-aug-06, om 21:18 heeft Reid Spencer het volgende geschreven: > I looked over your patch and it looks good. I applied a patch based on > yours. The llvm-ld tool now uses the PluginLoader just like the opt > tool. It will also run some cleanup passes after the loaded plugins > run > to ensure cruft is removed. OK, thanks. Your patch seems to work, although I also get

Hi, Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven: >> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build >> with the header files using uintptr_t (not recognised as a type). >> Putting "#include <stdint.h>" in include/llvm/BasicBlock.h (llvm) >> and in "include/llvm/ValueSymbolTable.h" (frontend)

Hi, I've written a couple of passes, and I intend to use them using llvm-ld (loading works fine). However, I can't seem to figure out how to put them first, i.e. before all other optimizations (inlining, internalizing, ... should only kick in after my passes). Omitting AnalysisUsage::setPreservesAll() doesn't help and there is no AnalysisUsage::invalidateAll(). Does anybody know

Hi, What's the best way to clone a Function (deep copy, not shallow)? Apparently only Instruction-classes feature a clone()-method, and there is no dedicated copy constructor/operator= for Function either. Kind regards, Bram Adams GH-SEL, INTEC, Ghent University

Hi, Op 26-mei-07, om 23:14 heeft Chris Lattner het volgende geschreven: > Shouldn't these symbols get "common" linkage, aka llvm weak linkage? > > Are you building the source with -fno-common? Yes. What does this mean? Kind regards, Bram Adams GH-SEL, INTEC, Ghent University (Belgium)

Hi, Op 30-mei-07, om 06:31 heeft Chris Lattner het volgende geschreven: >> when I do: llc file.bc -march=c -o file.c > > The C backend doesn't support all target-specific intrinsics. OK (http://llvm.org/bugs/show_bug.cgi?id=1481). > Please file a bug with this in a self-contained .c file. Thanks! Has happened: http://llvm.org/bugs/show_bug.cgi?id=1482. > Very strange.

Hi, Op 13-aug-03, om 19:35 heeft Chris Lattner het volgende geschreven: > On Mon, 14 Aug 2006, Devang Patel wrote: >> I have installed LinkTimeOptimization.html document in doc >> directory to describe LTO interface. > > Here's a link: :) > http://llvm.org/docs/LinkTimeOptimization.html Does the LTO-interface function already, or is functionality currently

On Sun, 2006-08-13 at 21:18 +0200, Bram Adams wrote: > Hi, > > Apparently there are two bugs in tools/llvmc/c: This tool is, as yet, unfinished. > > /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item > /.../llvm/tools/llvmc/c:28: Error: Expecting a program name > /.../llvm/tools/llvmc/c had 2 errors. Terminating. > > The first error relates to

Hi, Op 3-okt-06, om 20:48 heeft Chris Lattner het volgende geschreven: > You'd have to change it to something like: > > void foo(int X, ...) { > P = va_start(); > bar(X, P); > } > > void bar(int X, valist P) { > use(P); > } Can the other va_...-intrinsics be used in bar as were the "P = va_start" in bar? The va_start probably is unnecessary

Hi, Today I downloaded LLVM 1.8 (until yesterday I used 1.7) and I tried to build it (Slackware 10.2 with default GCC 3.3.6). However, the build process fails each time it reaches lib/Target/XXX/XXXISelDAGToDAG.cpp for all backends (XXX=X86, ARM, ...), e.g. like: /.../llvm-build/lib/Target/ARM/ARMGenDAGISel.inc:145: error: syntax error before `{' token ... [lots of other errors

Hi, Today I managed to link ioquake3, but generating a binary does not work yet. 1) On OSX, I get: Error: Code generator does not support intrinsic function 'llvm.ppc.altivec.lvsl'! when I do: llc file.bc -march=c -o file.c 2) On Linux X86, llc does not give any problem, but I get this while compiling the generated .c file: error: unknown register name 'S' in