similar to: [LLVMdev] Struct parameter

On Tue, Jul 19, 2011 at 10:12:47AM +0100, Jay Foad wrote: > On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote: > > Looks like that break came > > from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 > > Judging by this ArrayRef ctor you should be able to simplify those calls by > > changing the last two arguments from

I've been trying to package DragonEgg for Fedora Linux. Fedora 16 has LLVM 2.9 and GCC 4.6, but not the necessary GCC patches. If I build LLVM 3.0 on Fedora 16, then I can build DragonEgg 3.0, and it works fine. However, I can't submit that to the repository. On the other hand, Fedora 17, which just entered Beta, has LLVM 3.0 and GCC 4.7. I wasn't able to build DragonEgg 3.0

On Oct 2, 2007, at 1:03 AM, Domagoj Babic wrote: > Hi all, > > I have the same problem. My guess is that when a structure > is passed as a parameter, you cast it into an array for optimization > reasons (less parameters, less stack space). This is not an optimization. This behavior is to be ABI complaint when emitting code for your OS. That said, this is not a very good way to

Evan Cheng <evan.cheng at apple.com> writes: >> I'll be interested on hearing ideas about how to determine how a >> function returns a small struct, without knowing the internals of the >> struct. > Take a look at llvm-gcc. Look for HandleAggregateShadowArgument. This does not qualify as "without knowing the internals of the struct" :-)

> struct T { > struct T (*p)(void); > } t; This testcase also generates infinite recursion when we use llvm-gcc for arm-target. Because return type of function pointer p's is struct type T which has one element, llvm-gcc for arm target calls a function which tries to chang aggregate return type to inner element. (For example, C.HandleAggregateResultAsScalar(Ty); -->

Hi all, I have the same problem. My guess is that when a structure is passed as a parameter, you cast it into an array for optimization reasons (less parameters, less stack space). This is, certainly, a reasonable optimization, but makes inter-procedural static analysis more complex. Is there a way to disable it (my guess is that this should be doable by passing some parameter to llvm-gcc)? If

On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote: > Looks like that break came > from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 > Judging by this ArrayRef ctor you should be able to simplify those calls by > changing the last two arguments from "&foo, 1" to, simply, "foo". I've done this in r135472. Jay.

Hi everybody! I recently started using llvm in a project on inferring additional information about pointers based on their types, casts, etc. The following simple example is giving me a headache :): typedef struct { int a; short b, c; int d, e, f; } foo; void bar(foo f) { short s; s = f.b; } int main(void) { foo p; bar(p); } Because llvm doesn't allow structures and arrays

Take a look at llvm-gcc. Look for HandleAggregateShadowArgument. Evan On Mar 26, 2008, at 10:31 AM, Óscar Fuentes wrote: > Óscar Fuentes <ofv at wanadoo.es> writes: > >> BTW, -fpcc-struct-return solves the case that motivated this thread. > > -fpcc-struct-return is an ABI change, hence it requires "compiling the > world". Not acceptable. > > I'll

On Sat, Jul 9, 2011 at 4:27 PM, Chris Lattner <clattner at apple.com> wrote: > I'm sorry, I've been away from the computer. I'll investigate this in the next half hour.  Thanks for the test cases! One more testcase, which might be of interest; crashes clang on x86-64: struct T { struct T (*p)(void); } t; -Eli

On Jul 9, 2011, at 4:35 PM, Eli Friedman wrote: > On Sat, Jul 9, 2011 at 4:27 PM, Chris Lattner <clattner at apple.com> wrote: >> I'm sorry, I've been away from the computer. I'll investigate this in the next half hour. Thanks for the test cases! > > One more testcase, which might be of interest; crashes clang on x86-64: > > struct T { > struct T

Hi all, sorry to have sent the same question around. I am quite desperately looking for a solution to this problem and I figured the mailing list is the best bet. In my code, I generate the following function: define i32 @gl.qi([500 x i32] %x, i32 %i) { entry: %x. = alloca [500 x i32] %i. = alloca i32 %0 = alloca [500 x i32] store [500 x i32] %x, [500 x i32]* %x. store i32 %i, i32*

Hi, Browse[1]> d4 EVDO_Rev Session_Setup FCA bin counts 50 NA 0 5 1 1 51 NA 0 5 2 1 52 NA 0 5 3 1 53 NA 0 5 4 1 54 NA 0 5 5 1 55 NA 0 5 6 1 56 NA 0 5 7 1 57 NA 0 5 8

This makes is_gpxe() recognize gPXE's COMBOOT implementation as gPXE. Previously, is_gpxe() only recognized PXELINUX loaded from gPXE. Signed-off-by: Daniel Verkamp <daniel at drv.nu> --- com32/include/syslinux/config.h | 1 + com32/lib/sys/gpxe.c | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/com32/include/syslinux/config.h

Hello, everyone I have a piece of code that looks like this: mrets <- merge(mrets, BMM.SR=apply(mrets, 1, MyFunc, ret="BMM.AV120", stdev="BMM.SD120")) mrets <- merge(mrets, GM1.SR=apply(mrets, 1, MyFunc, ret="GM1.AV120", stdev="GM1.SD120")) mrets <- merge(mrets, IYC.SR=apply(mrets, 1, MyFunc, ret="IYC.AV120",

Hal Finkel <hfinkel at anl.gov> wrote on 16.03.2015 17:56:20: > If you want to do it at a clang level, the right thing to do is to > fixup the ABI lowerings for pointers to keep them pointers in this case. > So this is an artifact of the way that we pass structures, and > constructing a general solution at the ABI level might be tricky. > I've cc'd Uli, who did most

Hi! I created a bug report (https://llvm.org/bugs/show_bug.cgi?id=23712) for this failure but then I realized that my approach may be wrong. The following D source contains a lazy variable: void bar(lazy bool val) { val(); } The lazy variable val is translated to a delegate. The signature and the first IR lines are: define void @_D7opover23barFLbZv({ i8*, i1 (i8*)* } %val_arg) #0 {

On Mon, Mar 16, 2015 at 9:56 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > so just using pointer types instead of i64 will help common cases, but > will not address the general issue. Now part of this does some down to > using array parameters as a substitute for byval/direct parameters. As I > recall, this was done because it allowed a natural partial decomposition >

Hi! I have two dimensional dataset which has and I need to decide if a point lies in some "confidence level". If a point has low confidence/density it can be anomaly which I need to find. For example: #load library library(sm) #get some data x.locs = c(74, 74.5, 75, 77,74.5) y.locs = c(64, 63.5, 63, 61,61.5) points = cbind(x.locs, y.locs) #plot it plot(points) #get points density

Hola Alguien sabe como descargar una lista de librerías de R en formato zipeado. Por ejemplo quiero descargar las librerías (lme4, latticeExtras, Biobase,....., etc,etc) en formato zipeado. Se que puedo hacerlo una por una desde el cran pero quisiera tener un procedimiento para hacerlo automáticamente. Prof. Julio Di Rienzo Estadística y Biometría FCA- U.N. Córdoba