search for: pr14988

...quence, llvm.objectsize.i64(p) returns 6 (the entire *.ll is attached to the mail). Is this correct? Shouldn't the "object" refer to the entire block of memory being allocated? (char*) p = malloc(56) llvm.objectisize.i32(p+50); Thanks Shuxin This question is related to PR14988 (failure in bootstrap build with LTO). Part of the reason is that the compiler interpret the pretty vague team "object" in different ways -- the "object" suggested by line 359 @ figure 1 is just a part of the "object" implied by Figure 2. I try to fix the problem...

...*.ll is attached to the mail). > Is this correct? Shouldn't the "object" refer to the entire block of > memory being allocated? > > (char*) p = malloc(56) > llvm.objectisize.i32(p+50); > > Thanks > Shuxin > > > > This question is related to PR14988 (failure in bootstrap build > with LTO). Part of the reason is that > the compiler interpret the pretty vague team "object" in different > ways -- the "object" suggested by > line 359 @ figure 1 is just a part of the "object" implied by Figure 2. > &...

...e on the "p+50" pointer. See http://gcc.gnu.org/onlinedocs/gcc/Object-Size-Checking.html for intended use. >> (char*) p = malloc(56) >> llvm.objectisize.i32(p+50); >> >> Thanks >> Shuxin >> >> >> >> This question is related to PR14988 (failure in bootstrap build with LTO). >> Part of the reason is that >> the compiler interpret the pretty vague team "object" in different ways -- the "object" suggested by >> line 359 @ figure 1 is just a part of the "object" implied by Figure 2. &gt...

...http://gcc.gnu.org/onlinedocs/gcc/Object-Size-Checking.html for intended use. > >>> (char*) p = malloc(56) >>> llvm.objectisize.i32(p+50); >>> >>> Thanks >>> Shuxin >>> >>> >>> >>> This question is related to PR14988 (failure in bootstrap build with LTO). >>> Part of the reason is that >>> the compiler interpret the pretty vague team "object" in different ways -- the "object" suggested by >>> line 359 @ figure 1 is just a part of the "object" implied by F...

...Size-Checking.html for intended use. >> >>>> (char*) p = malloc(56) >>>> llvm.objectisize.i32(p+50); >>>> >>>> Thanks >>>> Shuxin >>>> >>>> >>>> >>>> This question is related to PR14988 (failure in bootstrap build with LTO). >>>> Part of the reason is that >>>> the compiler interpret the pretty vague team "object" in different ways -- the "object" suggested by >>>> line 359 @ figure 1 is just a part of the "object"...

...gt;>> >>>>> (char*) p = malloc(56) >>>>> llvm.objectisize.i32(p+50); >>>>> >>>>> Thanks >>>>> Shuxin >>>>> >>>>> >>>>> >>>>> This question is related to PR14988 (failure in bootstrap build with LTO). >>>>> Part of the reason is that >>>>> the compiler interpret the pretty vague team "object" in different ways -- the "object" suggested by >>>>> line 359 @ figure 1 is just a part of the "o...