search for: gordonhenriksen

On Mon, Apr 28, 2008 at 2:13 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > > If so, then a Collector plugin would need to have info about every > > supported backend lays out the runtime stack? > > Yes. This information is actually available in a target-independent > fashion with LLVM, so the Collector interface is target-i...

2008/7/26 Gordon Henriksen <gordonhenriksen at me.com>: > I'm not sure the purpose of doing so—llvm::Collector (poorly named; > I'm open to suggestions) exists only in the compiler, not at runtime > in the compiled program. You should need access to it at runtime no > more than you might need access to an instance of l...

On 2008-04-28, at 21:19, Lane Schwartz wrote: > On Mon, Apr 28, 2008 at 2:13 PM, Gordon Henriksen <gordonhenriksen at mac.com > > wrote: > >>> If so, then a Collector plugin would need to have info about every >>> supported backend lays out the runtime stack? >> >> Yes. This information is actually available in a target-independent >> fashion with LLVM, so the C...

On Jul 26, 2008, at 12:14, Simon Ask Ulsnes wrote: > 2008/7/26 Gordon Henriksen <gordonhenriksen at me.com>: >> I'm not sure the purpose of doing so—llvm::Collector (poorly named; >> I'm open to suggestions) exists only in the compiler, not at >> runtime in the compiled program. You should need access to it at >> runtime no more than you might need acce...

On Sun, Apr 27, 2008 at 9:34 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > As for the compiler plugin interface, I suggest you ignore it > initially and use the provided shadow-stack option for the time being. > The shadow stack generates significantly suboptimal code, but will let > you avoid writing some platform-specific code. In...

Thanks for the review Gordon. On Tue, Nov 1, 2011 at 2:21 AM, Gordon Henriksen <gordonhenriksen at mac.com>wrote: > On 2011-10-31, at 17:21, Nicolas Geoffray wrote: > > > Here's a patch to allow a GCStrategy to customize the places where it > wants to insert safe points. I'm not sure who maintains the GC code today > in LLVM (I'd be happy to take ownership, i...

On Nov 1, 2011, at 4:47 AM, Nicolas Geoffray <nicolas.geoffray at gmail.com> wrote: > Thanks for the review Gordon. > > On Tue, Nov 1, 2011 at 2:21 AM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On 2011-10-31, at 17:21, Nicolas Geoffray wrote: > > > Here's a patch to allow a GCStrategy to customize the places where it wants to insert safe points. I'm not sure who maintains the GC code today in LLVM (I'd be happy to take ownership, if needed)...

On Mon, Apr 28, 2008 at 8:31 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On 2008-04-28, at 21:19, Lane Schwartz wrote: > > > On Mon, Apr 28, 2008 at 2:13 PM, Gordon Henriksen <gordonhenriksen at mac.com > > > wrote: > > > >>> If so, then a Collector plugin would need to have info about every > &gt...

On Sun, Feb 28, 2010 at 9:55 AM, Gordon Henriksen <gordonhenriksen at me.com> wrote: > In practice, so long as frame pointers are not elided, a handful of lines of > assembly per platform should get you a stack walker. If frame pointers are > elided, however, you're looking at parsing DWARF to find out where it was > saved, which is probably too...

2008/7/24 Gordon Henriksen <gordonhenriksen at me.com>: >> OK, so for instance if I wanted to be able to use the GC from a C >> frontend (presumably by using llvm_gc_allocate?), do the C functions >> need this attribute as well? > > Yes. I forgot I still needed an answer to my original question. :-P So, I have to...

On Wed, Jun 11, 2008 at 11:49 AM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > Could you please update to r52213 or later in svn and check whether > this error is resolved with your gcc? Latest trunk fixes that error. Next problem :) llvm[3]: Building ARM.td register information header with tblgen llvm[3]: Building ARM.td register names with tbl...

Thank you so much for your help! I now have a much clearer idea of how to proceed. :-) This just keeps getting more interesting. - Simon 2008/7/26 Gordon Henriksen <gordonhenriksen at me.com>: > On Jul 26, 2008, at 12:14, Simon Ask Ulsnes wrote: > > 2008/7/26 Gordon Henriksen <gordonhenriksen at me.com>: > > I'm not sure the purpose of doing so—llvm::Collector (poorly named; I'm open > to suggestions) exists only in the compiler, not at runt...

On Apr 28, 2008, at 14:28, Lane Schwartz wrote: > On Sun, Apr 27, 2008 at 9:34 PM, Gordon Henriksen > <gordonhenriksen at mac.com> wrote: > >> As for the compiler plugin interface, I suggest you ignore it >> initially and use the provided shadow-stack option for the time >> being. The shadow stack generates significantly suboptimal code, >> but will let you avoid writing some pla...

Hi Talin, On Feb 27, 2010, at 22:06, Talin wrote: > The main problem with shadow-stack is that it's not thread-safe. It sounds like you've outgrown it, then. > What about modifying the shadow-stack to use a thread-local linked list? > Another alternative is to add an additional parameter to every function containing the address of the head of the stack frame list. and have

--- On Thu, 1/3/08, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > > On Jan 2, 2008, at 05:57, Kamal R. Prasad wrote: > > > (im new to LLVM , so pl excuse if this is a naive q). > > Welcome! > thanks > > Can someone provide info on what runtime optimizations > are done in > > LLVM? > > Yo...

...ynamic libraries. The space saving is huge though: 1350MiB vs 723MiB and the IO load is probably greatly reduced. I've added a hackish script that patches LLVM 2.3 to use dynamic libraries if anyone wants it. Just run it after configuring. On Tue, Oct 7, 2008 at 10:50 AM, Gordon Henriksen <gordonhenriksen at me.com>wrote: > On Oct 6, 2008, at 15:52, Yale Zhang wrote: > > > Hi everyone. I'm mainly build the debug versions of lli and opt > > which are huge and take up to 10 seconds to build. It seems there is > > no option in configure to allow dynamic linking. Before I...

On Mon, May 12, 2008 at 7:55 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On May 12, 2008, at 02:58, Mahadevan R wrote: > > >> Consider the case where a function creates and populates a Module, > >> stuffs it in an ExistingModuleProvider for the JIT, then returns > >> the ModuleProvider, dropping direct referenc...

Pending positive confirmation in http://llvm.org/PR2886, I'd recommend that r57974 and r57976 be pulled into the 2.4 release branch and configure regenerated there. Begin forwarded message: > From: Gordon Henriksen <gordonhenriksen at mac.com> > Date: October 22, 2008 08:40:40 EDT > To: llvm-commits at cs.uiuc.edu > Subject: [llvm-commits] [llvm] r57974 - /llvm/trunk/autoconf/ > configure.ac > Reply-To: Commit Messages and Patches for LLVM <llvm-commits at cs.uiuc.edu > > > > Author: gordon...

On Tue, May 13, 2008 at 1:22 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On 2008-05-13, at 02:12, Mahadevan R wrote: > > >>> That's not how the object works... > > > > Gordon, I think I can make it work if we have the following additional > > function in LLVM-C: > > > > LLVMModuleRef LLVMG...

...quot;\n\nRunning foo: " << std::flush; std::vector<GenericValue> noargs; GenericValue gv = EE->runFunction(FooF, noargs); std::cout << "Result: " << gv.IntVal.toStringUnsigned(10) << "\n"; return 0; } 2008/8/19, Gordon Henriksen <gordonhenriksen at me.com>: > > On Aug 19, 2008, at 13:36, kirill havok wrote: > > I got very interested in LLVM project, and I decided to start writing my own > scripting language based on it. By studying the documentation, I could not > find how to call external function, written in C. That...