search for: peufeu

On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >> There are essentially two ways to "solve" this issue: one is >> type-based alias analysis, i.e. assuming "double" and "int" don't >> alias; LLVM doesn't implement this at the moment.  The other is to >> attempt to analy...

> There are essentially two ways to "solve" this issue: one is > type-based alias analysis, i.e. assuming "double" and "int" don't > alias; LLVM doesn't implement this at the moment. The other is to > attempt to analyze the loop and prove that %indvar.i is never > negative; LLVM doesn't implement anything like this at the moment >

On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>> There are essentially two ways to "solve" this issue: one is >>> type-based alias analysis, i.e. assuming "double" and "int" don't >>> alias; LLVM doesn't implement this at the moment.  The other is to >>>...

On 06/17/2010 06:19 PM, Jeffrey Yasskin wrote: > On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> wrote: >> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>>> There are essentially two ways to "solve" this issue: one is >>>> type-based alias analysis, i.e. assuming "double" and "int" don't >>>> alias; LLVM doesn't implement this at the moment. The other is to &...

On Jun 17, 2010, at 10:42 AM, Andrew Haley wrote: > On 06/17/2010 06:19 PM, Jeffrey Yasskin wrote: >> On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> wrote: >>> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>>>> There are essentially two ways to "solve" this issue: one is >>>>> type-based alias analysis, i.e. assuming "double" and "int" don't >>>>> alias; LLVM doesn't implement this at the moment. The o...

...in the standard some time ago, but could not find it. On Thu, Jun 17, 2010 at 6:19 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> wrote: >> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>>> There are essentially two ways to "solve" this issue: one is >>>> type-based alias analysis, i.e. assuming "double" and "int" don't >>>> alias; LLVM doesn't implement this at the moment.  The other is to &...

...om> wrote: > > On Jun 17, 2010, at 10:42 AM, Andrew Haley wrote: > > On 06/17/2010 06:19 PM, Jeffrey Yasskin wrote: > > On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> > wrote: > > On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: > > There are essentially two ways to "solve" this issue: one is > > type-based alias analysis, i.e. assuming "double" and "int" don't > > alias; LLVM doesn't implement this at the moment.  The other is to > > attempt to a...

I'm hitting a strange pointer aliasing "bug". Here is a test case : /* SOURCE CODE */ #define little_list_size 8 class LittleList1 { public: int _length; double _data[ little_list_size ]; LittleList1( int length ) { _length = length; for( int i=0; i<length; i++ ) _data[i] = 0; } }; class LittleList2 { public: int _length; double _data[ little_list_size ];

...17, 2010, at 10:42 AM, Andrew Haley wrote: >> >> On 06/17/2010 06:19 PM, Jeffrey Yasskin wrote: >> >> On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> >> wrote: >> >> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >> >> There are essentially two ways to "solve" this issue: one is >> >> type-based alias analysis, i.e. assuming "double" and "int" don't >> >> alias; LLVM doesn't implement this at the moment. The other i...

On Jun 17, 2010, at 12:22 AM, Eli Friedman wrote: > On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>> There are essentially two ways to "solve" this issue: one is >>> type-based alias analysis, i.e. assuming "double" and "int" don't >>> alias; LLVM doesn't implement this at the moment. The other is to >>>...

On Wed, Jun 16, 2010 at 1:39 PM, Pierre C <lists at peufeu.com> wrote: > > I'm hitting a strange pointer aliasing "bug". Here is a test case : > > /* SOURCE CODE */ > > #define little_list_size 8 > > class LittleList1 { > public: >        int     _length; >        double  _data[ little_list_size ]; > &gt...

...of pointer arithmetic.) Daveed > > On Thu, Jun 17, 2010 at 6:19 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: >> On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> wrote: >>> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>>>> There are essentially two ways to "solve" this issue: one is >>>>> type-based alias analysis, i.e. assuming "double" and "int" don't >>>>> alias; LLVM doesn't implement this at the moment. The o...

...drew Haley wrote: >>> >>> On 06/17/2010 06:19 PM, Jeffrey Yasskin wrote: >>> >>> On Thu, Jun 17, 2010 at 12:22 AM, Eli Friedman <eli.friedman at gmail.com> >>> wrote: >>> >>> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote: >>> >>> There are essentially two ways to "solve" this issue: one is >>> >>> type-based alias analysis, i.e. assuming "double" and "int" don't >>> >>> alias; LLVM doesn't implement this at the...

>> Consider a case like the following: >> struct X { int a; int b[10]; }; >> int f(struct X* a) { a->b[-1] = 1; return a->a; } >> >> This is technically illegal code, but various programs depend on >> constructs like this working. >> Actually if you want to do bit-casting in C the usual way is to very carefully use an union which informs the

Hello ! I wanted to experiment with partial evaluation and llvm seems to be the right tool for this, but since I'm new to it of course I'm a bit lost ! I'll try to explain what I want to do in the simplest possible way : I have a C program. In this program, there is a function f( a,b ). I have a value A for a. I want to specialise f() so I get a function fA( b ) which is the same as

---------------------------------------------------- Server : Athlon 64 3000+ ; 512MB Ram ; lots of disks ; nforce3 chipset ; integrated nvidia gigabit NIC. Gentoo 2.6.15 linux 64-bits ; Samba 3.0.14a-r2 ---------------------------------------------------- Clients : Laptop with Centrino Pentium-M, 100 Mbps NIC, running Windows XP Family Desktop with Athlon 64 3200+ ; 1G DDR Dual Channel