similar to: [LLVMdev] Modifying Instruction Class

Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Modifying Instruction Class"

2007 Oct 09
1
high CPU usage with TAR files
I am trying to use rsync to backup our Linux server and when the rsync is running it uses 1-2% CPU for most operations until it reaches a tar file (or another file archive), then the CPU usage increases to 90%. I am assuming that rsync is looking at the individual files in the tar archive and seeing if any have changed instead of looking at the mod time and file size. I'm sure this is a
2008 Feb 01
1
[LLVMdev] Code Extractor Issue
I'm having an issue with the CodeExtractor. When I try to extract the lone basic block from the following function, I get an assertion error. define i32 @test(i32 %x) { %tmp = call i32 @test3( i32 %x ) ; <i32> [#uses=1] ret i32 %tmp } The assertion error is: lli: Dominators.cpp:71: void llvm::DominatorTree::splitBlock(llvm::BasicBlock*): Assertion
2010 Jun 19
3
[PATCH 1/1] ocfs2 fix o2dlm dlm run purgelist
There are two problems in dlm_run_purgelist 1. If a lockres is found to be in use, dlm_run_purgelist keeps trying to purge the same lockres instead of trying the next lockres. 2. When a lockres is found unused, dlm_run_purgelist releases lockres spinlock before setting DLM_LOCK_RES_DROPPING_REF and calls dlm_purge_lockres. spinlock is reacquired but in this window lockres can get reused. This
2010 Feb 07
3
[LLVMdev] Help with Mac OS X 10.6.2 build
Greetings, I am having trouble getting the Kaleidoscope example to build from tutorial #3 on Mac OS X 10.6.2. I didn't have too much trouble getting llvm-2.6 and llvm-gcc-frontend to build. Thanks for the help. Here are the steps I followed: Environment variables for build export LLVMOBJDIR=/opt/llvm export TARGETOPTIONS='--with-arch=nocona --with-tune=generic' export
2010 Feb 07
0
[LLVMdev] Help with Mac OS X 10.6.2 build
Hi, Try these scripts to build llvm and llvm-gcc. It's the ones I use and I managed to get them to work when I saw another build script using those CFLAGS. They compile llvm and stuff using only x86_64, but you can then generate code for i386 (just use a different backend). The configuration options are at the top of the scripts and they install llvm and llvm-gcc to ~/llvm. Regards,
2007 Sep 17
2
No subject
Hi, when trying to install openssh I get the following errors. Any idea of why? This is on a mac 10.4.10 system, and with the 4.7p1 version. Appreciate any tips. Thanks, Anil if test ! -z ""; then \ /usr/bin/perl ./fixprogs ssh_prng_cmds ; \ fi (cd openbsd-compat && make) make[1]: Nothing to be done for `all'. gcc -g -O2 -Wall -Wpointer-arith -Wuninitialized
2005 Mar 09
4
[LLVMdev] Recursive Types using the llvm support library
----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, March 08, 2005 6:31 PM Subject: Re: [LLVMdev] Recursive Types using the llvm support library > On Tue, 8 Mar 2005, Vladimir Merzliakov wrote: > >>>> An example where something really simple like the
2005 Mar 09
0
[LLVMdev] Recursive Types using the llvm support library
On Wed, 9 Mar 2005, Vladimir Merzliakov wrote: > I create test program and assert failed in it: > > { \2 *, sbyte * } > Assertion failed: (!NewSTy->isAbstract()), function main, file > /usr/home/wanderer/work/LLVMTest/obj/../src/tools/tool/Test.cc, line 28. > > Testcase source attached. Thanks, that definitely is a bug. Patch here:
2005 Mar 08
2
[LLVMdev] Recursive Types using the llvm support library
>> An example where something really simple like the line below was output >> would be perfect. >> >> %struct.linked_list = type { %struct.linked_list*, %sbyte* } > > Use something like this: > > PATypeHolder StructTy = OpaqueType::get(); > std::vector<const Type*> Elts; > Elts.push_back(PointerType::get(StructTy)); >
2005 Mar 21
2
[LLVMdev] Recursive Types using the llvm support library
On Sun, 20 Mar 2005, John Carrino wrote: > On Wed, Mar 09, 2005 at 04:05:32PM +0300, Vladimir Merzliakov wrote: >>>> Is assert(!NewSTy->isAbstract()) must pass after this line? >>> >>> In this case, yup. >>> >> I create test program and assert failed in it: >> >> { \2 *, sbyte * } > > How do I decode the \2 in this? I am
2005 Mar 08
0
[LLVMdev] Recursive Types using the llvm support library
On Tue, 8 Mar 2005, Vladimir Merzliakov wrote: >>> An example where something really simple like the line below was output >>> would be perfect. >>> >>> %struct.linked_list = type { %struct.linked_list*, %sbyte* } >> >> Use something like this: >> >> PATypeHolder StructTy = OpaqueType::get(); >> std::vector<const
2005 Mar 21
0
[LLVMdev] Recursive Types using the llvm support library
On Sun, Mar 20, 2005 at 07:01:55PM -0600, Chris Lattner wrote: > On Sun, 20 Mar 2005, John Carrino wrote: > > >On Wed, Mar 09, 2005 at 04:05:32PM +0300, Vladimir Merzliakov wrote: > >>>>Is assert(!NewSTy->isAbstract()) must pass after this line? > >>> > >>>In this case, yup. > >>> > >>I create test program and assert
2015 Jan 14
3
[LLVMdev] Crash on invalid during LLVMContext destruction MDNode::dropAllReferences
Hi Duncan, I came across something like the following recently which I guess might be related to your recent work. Any ideas? $ clang++-tot -cc1 crash_on_invalid.cpp -g -emit-obj -fexceptions -fcxx-exceptions crash_on_invalid.cpp:13:1: error: C++ requires a type specifier for all declarations x; ^ 1 error generated. *** Error in `clang++-tot': corrupted double-linked list: 0x000000000754f340
2007 Nov 05
12
Error installing Mongrel on Solaris 9
Hi all, We''ve installed RoR on Solaris 9, and are attempting to install Mongrel using the following command:gem install mongrelgetting error "SSL is not installed on this system".All other gems (including Rake) installed fine.Any suggestions?Thanks,Brian _________________________________________________________________ Boo!?Scare away worms, viruses and so much more! Try
2005 Mar 21
1
[LLVMdev] Recursive Types using the llvm support library
On Sun, 20 Mar 2005, John Carrino wrote: >> In practice, this is leads to a horrible mess, as you've noticed. As >> such, I'd suggest using Module::addTypeName to give these things names so >> that you have a hope to understand them and so they are more compact :) > > I took your advide and used Module::addTypeName which is a great idea > that I didn't know
2005 Mar 21
0
[LLVMdev] Recursive Types using the llvm support library
On Wed, Mar 09, 2005 at 04:05:32PM +0300, Vladimir Merzliakov wrote: > >>Is assert(!NewSTy->isAbstract()) must pass after this line? > > > >In this case, yup. > > > I create test program and assert failed in it: > > { \2 *, sbyte * } How do I decode the \2 in this? I am creating types through this interface and I get quite a mess seen below. And this is
2004 Jul 10
3
[LLVMdev] Re: [llvm-commits] CAUTION: Type != Value
In VMCore/Module.cpp i found line (254): ((Value*)Ty)->setName(Name, &ST); Type is not Value now and for me this code call llvm::DerivedType::addAbstractTypeUser (I think it have same index in Type VMT in as setName in Value VMT) with random argument values and terminated with assert fail: Assertion failed: (isAbstract() && "addAbstractTypeUser: Current type not
2006 Sep 12
1
[LLVMdev] ICE in LLVM GCC4 Front End
[Reposted from llvm-bugs mailing list. Also has an updated, hopefully better, patch associated with it.] Hi, The following program causes the LLVM GCC4 front end to ICE: struct A { virtual ~A(); }; template <typename Ty> struct B : public A { ~B () { delete [] val; } private: Ty* val; }; template <typename Ty> struct C : public A { C (); ~C (); }; template
2004 Mar 27
1
[LLVMdev] Extending LLVM
On Fri, 2004-03-26 at 14:57, Chris Lattner wrote: > On Fri, 26 Mar 2004, Reid Spencer wrote: > > > Would people other than myself find it useful to have a standardized > > extension framework for LLVM? I'm thinking of something that would allow > > new LLVM instructions, fundamental types, structured types, etc. This > > would require significant work to allow
2004 Jul 10
0
[LLVMdev] Re: [llvm-commits] CAUTION: Type != Value
Vladimir, As you noted, the cast to Value* from (I presume) Type* is now invalid as there is no inheritance relationship. You can give a type a name by converting: Ty->setName(Name, &ST) to: ST.insert(Name, Ty) Hope that helps. Reid. On Sat, 2004-07-10 at 07:01, Vladimir Merzliakov wrote: > In VMCore/Module.cpp i found line (254): > > ((Value*)Ty)->setName(Name,