search for: magi

On Wed, 20 Jun 2007, Sandro Magi wrote: > To this end, are there any implicit allocations being done by > generated LLVM code, other than the system stack? heap allocations? Only malloc/free. Note that the compiler does generate calls to runtime libraries (e.g. libstdc++ and libgcc), we don't have control over when...

On Sun, 8 Jul 2007, Sandro Magi wrote: > How about if I were to use LLVM's JIT? I suspect plenty of allocations > are performed in the JIT. The JIT does a ton of heap allocation. There is no way to approximate it from the code you give it. -Chris > Sandro > > On 6/20/07, Chris Lattner <sabre at nondot.o...

...t traced it down > to this commit. > > e5a4b0bb803b39a36478451eae53a880d2663d5b is the first bad commit > commit e5a4b0bb803b39a36478451eae53a880d2663d5b here is the gist of that commit... https://lkml.org/lkml/2014/12/5/25 here is the output of rsync when the error occurs. root at Magi-01:~# rsync -a /export/test/* /export/test2 rsync: [sender] write error: Broken pipe (32) rsync error: error in socket IO (code 10) at io.c(820) [sender=3.1.1] root at Magi-01:~# here is the output of rsync when executed via gdb root at Magi-01:~# gdb /usr/bin/rsync GNU gdb (Debian 7.11.1-2) 7.11...

.... My public share in smb.conf is: [publica] available = yes browseable = yes comment = public folder guest ok = yes path = /home/public read only = no writable = yes The problem is: The user Bob open any folder located in publica share, then create a new folder and insert new content. The user Magie open the folder created by Bob and your content is invisible for Magie and others users. Only Bob can view the contents!!! Help me please! ThanX!

...hould avoid using integers with bit widths larger than 64 bits (or perhaps 128)? Is there a hard rule for an integer being stack allocated, ie. one that doesn't depend on the current implementation details? Sandro On 6/18/07, Reid Spencer <rspencer at reidspencer.com> wrote: > Sandro Magi wrote: > > >Where does the storage for large bit width integers come from? Are > >very large numbers heap allocated? > > > > > The ConstantInt class stores integer values. Large or not they are > stored using an APInt object. APInt (lib/Support/APInt.cpp) uses an &g...

I'm having trouble achieving the results I want using a regular expression. I want to eliminate all characters that fall within square brackets as well as the brackets themselves, returning an "". I'm not sure if it's R's use of double slash escapes or something else that is tripping me up. If I only use one slash I get 1: '\[' is an unrecognized escape in a

On 6/18/07, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 18 Jun 2007, Sandro Magi wrote: > > Ok, so if I needed very precise control over the allocation of memory, > > then I should avoid using integers with bit widths larger than 64 bits > > (or perhaps 128)? Is there a hard rule for an integer being stack > > allocated, ie. one that doesn't depend o...

How about if I were to use LLVM's JIT? I suspect plenty of allocations are performed in the JIT. Sandro On 6/20/07, Chris Lattner <sabre at nondot.org> wrote: > On Wed, 20 Jun 2007, Sandro Magi wrote: > > To this end, are there any implicit allocations being done by > > generated LLVM code, other than the system stack? > > heap allocations? Only malloc/free. Note that the compiler does generate > calls to runtime libraries (e.g. libstdc++ and libgcc), we don't h...

On 7/10/07, Chris Lattner <sabre at nondot.org> wrote: > On Sun, 8 Jul 2007, Sandro Magi wrote: > > How about if I were to use LLVM's JIT? I suspect plenty of allocations > > are performed in the JIT. > > The JIT does a ton of heap allocation. There is no way to approximate it > from the code you give it. I don't need to approximate it, but I'd like t...

On Tue, 10 Jul 2007, Sandro Magi wrote: > On 7/10/07, Chris Lattner <sabre at nondot.org> wrote: >> On Sun, 8 Jul 2007, Sandro Magi wrote: >>> How about if I were to use LLVM's JIT? I suspect plenty of allocations >>> are performed in the JIT. >> The JIT does a ton of heap allocation. Th...

To this end, are there any implicit allocations being done by generated LLVM code, other than the system stack? Sandro On 6/18/07, Sandro Magi <naasking at gmail.com> wrote: > Given my recent posts, I think it's obvious that I'm trying to figure > out how to build a resource-aware VM for a high-level language. > > I've figured out adequate solutions for most of the problems I've > encountered, includin...

On Mon, 18 Jun 2007, Sandro Magi wrote: > Ok, so if I needed very precise control over the allocation of memory, > then I should avoid using integers with bit widths larger than 64 bits > (or perhaps 128)? Is there a hard rule for an integer being stack > allocated, ie. one that doesn't depend on the current implem...

Where does the storage for large bit width integers come from? Are very large numbers heap allocated? Sandro

...calling malloc with a large value will cause a real program to fail. This translation would seem to make potentially failing programs succeed. Seems counter-intuitive to me, but as I said, perhaps I just need to read up on this "as-if" rule. Sandro On Fri, May 2, 2008 at 1:55 PM, Sandro Magi <naasking at gmail.com> wrote: > > On Thu, May 1, 2008 at 6:54 PM, Chris Lattner <sabre at nondot.org> wrote: > > > > > I don't see how this could be true in general, without either > > > knowledge of the malloc implementation, which would be fine,...

Given my recent posts, I think it's obvious that I'm trying to figure out how to build a resource-aware VM for a high-level language. I've figured out adequate solutions for most of the problems I've encountered, including separate heaps, quotas, etc. However, I'm not sure how I can account for a thread's stack space. Given a language process (LP) running in a heap with a

...> e5a4b0bb803b39a36478451eae53a880d2663d5b is the first bad commit >> commit e5a4b0bb803b39a36478451eae53a880d2663d5b > > here is the gist of that commit... > > https://lkml.org/lkml/2014/12/5/25 > > here is the output of rsync when the error occurs. > > root at Magi-01:~# rsync -a /export/test/* /export/test2 > rsync: [sender] write error: Broken pipe (32) > rsync error: error in socket IO (code 10) at io.c(820) [sender=3.1.1] > root at Magi-01:~# > > here is the output of rsync when executed via gdb > > root at Magi-01:~# gdb /usr/bin/r...

On Thu, 1 May 2008, Sandro Magi wrote: >> If LLVM is able to eliminate all users of the malloc assuming the >> malloc succeeded (as in this case), then it is safe to assume the malloc >> returned success. > > I don't see how this could be true in general, without either > knowledge of the malloc...

On Tue, 14 Mar 2006, Sandro Magi wrote: >> consider all pointers to be in scope, without causing any "dead" pointers >> to mark objects. > > Does this mean some pointers from the roots might be null? Well sure, if they are null. e.g.: int *X = NULL; X would be null. Is that what you mean? > I f...

On Mon, 18 Jun 2007, Sandro Magi wrote: > Generated code. So the memory used for the integer at program runtime > is inlined into the allocation point then? So if I define a local > variable of type 'i1024', it will allocate a block of 1024 bits on the > stack, if I define a struct with an i1024, it will be in...

On 9/28/07, Chris Lattner <sabre at nondot.org> wrote: > > > Sorry, I meant to ask whether it's still necessary to keep F around, > > ie. to delete generated code. Is there a standard approach to garbage > > collecting code in LLVM? > > Machine code in the JIT buffer or the LLVM IR itself? > Assuming I don't need to keep around the IR version of a