Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] Cloning Function-objects"
2006 Sep 21
0
[LLVMdev] Cloning Function-objects
On Thu, 21 Sep 2006, Bram Adams wrote:
> 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.
Take a look at "llvm/Transforms/Utils/Cloning.h".
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2006 Aug 20
3
[LLVMdev] Weird behavior of llvm-ld
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
2006 Aug 20
0
[LLVMdev] Weird behavior of llvm-ld
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
2007 May 18
2
[LLVMdev] Antw.: 2.0 Pre-release tarballs online
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)
2006 Aug 20
2
[LLVMdev] Weird behavior of llvm-ld
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)
2006 Nov 15
0
[LLVMdev] 1.9 Prerelease Available for Testing
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?
2006 Nov 15
4
[LLVMdev] 1.9 Prerelease Available for Testing
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 ===
2006 Oct 05
3
[LLVMdev] Extracting all BasicBlocks of a Function into new Function
Hi,
Chris Lattner wrote:
> All the non-vastart calls can be anywhere. va_end in particular codegens
> to a noop on all targets llvm currently supports, fwiw.
>
Things go well, except for the following (pathological?) C program:
int va_double_sum(int count,...){
int i,sum=0;
va_list ap;
va_start(ap,count);
for(i=0;i<count;i++){
sum+=va_arg(ap,int);
}
va_end(ap);
2008 Jul 09
2
[LLVMdev] Add RTLD_GLOBAL to dlopen
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
2006 Oct 02
3
[LLVMdev] Extracting all BasicBlocks of a Function into new Function
Hi,
Op 2-okt-06, om 21:35 heeft Chris Lattner het volgende geschreven:
> I think the easiest way to do this is to do the 'complement' as you
> describe, but specially handle the varargs case. Basically you
> need to
> call va_start in the original function, and pass the valist pointer
> down.
> This shouldn't be too hard.
OK.
I've been rethinking my use
2007 May 26
2
[LLVMdev] Linking two external linkage GlobalValues
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)
2007 May 30
2
[LLVMdev] Code generation issues
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.
2006 Aug 14
2
[LLVMdev] link time optimization doc
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
2006 Aug 16
3
[LLVMdev] Problem with stock llvmc configuration for C
Hi,
Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven:
>
>> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful
>> variable by the llvmc configuration parser.
>
> Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around
> line
> 304. Also, they are recognized by the lexer. Its more likely that when
> you configured LLVM
2007 May 18
0
[LLVMdev] Antw.: 2.0 Pre-release tarballs online
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
2006 Sep 18
3
[LLVMdev] Manipulate order of optimizations in llvm-ld
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
2008 Jul 10
0
[LLVMdev] Add RTLD_GLOBAL to dlopen
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
2007 May 29
4
[LLVMdev] Code generation issues
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
2007 May 17
8
[LLVMdev] Antw.: 2.0 Pre-release tarballs online
Hi,
Op 15-mei-07, om 10:23 heeft Tanya M. Lattner het volgende geschreven:
1) Download llvm-gcc4 binary and llvm. Compile and run make check.
I did a debug build on OSX 10.4.9 and everything went fine.
Results of "make check" (see ppc.log):
=== Summary ===
# of expected passes 1630
# of unexpected failures 21
# of expected failures 2
2006 Aug 13
2
[LLVMdev] Problem with stock llvmc configuration for C
Hi,
Apparently there are two bugs in tools/llvmc/c:
/.../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 the following line(s):
lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \
%llvmgccdir%/lib/gcc/%llvmgccarch%
... the other one to: