similar to: [LLVMdev] Invalid call generated on 64-bit linux when calling native C function from IR

Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Invalid call generated on 64-bit linux when calling native C function from IR"

2008 Aug 27
2
[LLVMdev] Mandatory duplicated incoming nodes on phis
Hi, I noticed that if you create a switch with multiple cases going to the same destination, then if that destination contains phis you need to add the incoming value an equivalent number of times. The attached code seems wrong, but it compiles as correct, and removing the duplicated incoming node causes an error. Is this expected? Cheers, Gary -- http://gbenson.net/ -------------- next part
2011 Jun 28
2
[LLVMdev] Generating different assembly code for the same LLVM instruction depending on the metadata.
Hi LLVM devs, consider I've got an instrumentation pass that adds some code (say, function calls) before some memory access instructions and marks those calls with some special metadata. I want the compiler to lower the instrumentation code to a sequence of no-ops while generating the object code. For example, the assembly for the following code: 1 void _instr(); // the instrumentation
2010 Apr 02
2
[LLVMdev] Problem returning aggregate struct (complex number) by value
I'm trying to return an aggregate structure (a complex number, really) containing two 32-bit floats or two 64-bit doubles, by value. LLVM 2.6 compiled as 64-bit on OSX 10.6/x86-64. The IR I generate for a simple test case looks like this (float case): %0 = type { float, float } define %0 @test600() { entry: ret %0 { float 4.200000e+01, float 3.500000e+01 } } Running that through
2017 Feb 14
0
[PATCH v2 0/3] x86/vdso: Add Hyper-V TSC page clocksource support
On Tue, Feb 14, 2017 at 7:50 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > Thomas Gleixner <tglx at linutronix.de> writes: > >> On Tue, 14 Feb 2017, Vitaly Kuznetsov wrote: >> >>> Hi, >>> >>> while we're still waiting for a definitive ACK from Microsoft that the >>> algorithm is good for SMP case (as we can't
2011 Jun 08
1
Reference Class error message: may be caused by lazy evaluation?
Dear All, I came across an error message recently when constructing a reference class, an example is attached below, it looks like only if I call a specific method in advance, otherwise it cannot be found in defined method without using .self, this make it difficulty that sometimes in my initialize method, I need to call other method defined in the same reference class, the workaround for this is
2017 Feb 14
2
[PATCH v2 0/3] x86/vdso: Add Hyper-V TSC page clocksource support
Thomas Gleixner <tglx at linutronix.de> writes: > On Tue, 14 Feb 2017, Vitaly Kuznetsov wrote: > >> Hi, >> >> while we're still waiting for a definitive ACK from Microsoft that the >> algorithm is good for SMP case (as we can't prevent the code in vdso from >> migrating between CPUs) I'd like to send v2 with some modifications to keep
2017 Feb 14
2
[PATCH v2 0/3] x86/vdso: Add Hyper-V TSC page clocksource support
Thomas Gleixner <tglx at linutronix.de> writes: > On Tue, 14 Feb 2017, Vitaly Kuznetsov wrote: > >> Hi, >> >> while we're still waiting for a definitive ACK from Microsoft that the >> algorithm is good for SMP case (as we can't prevent the code in vdso from >> migrating between CPUs) I'd like to send v2 with some modifications to keep
2011 Apr 30
1
Reference Classes: Accessing methods via [[...]], bug?
I've been trying to use methods for reference classes via the notation "[[...]]" (X[["doSomething"]] rather than X$doSomething), but it failed to work. However, I did find that if you use the usual "$" notation first, "[[...]]" can be used afterwards. The following simple example illustrates the point: > setRefClass("Number", + fields =
2007 Oct 10
2
documentation of .C (PR#9948)
Full_Name: Martin Schlather Version: R version 2.7.0 Under development (unstable) (2007-10-01 r43043) OS: Linux Submission from: (NULL) (91.3.209.203) Hi, There are 2 dangers with using 'DUP=FALSE' mentioned: * formal arguments * lists Would you also mention a third one, namely that values in R are now only referenced whenever possible and not always copied; hence .C(...,
2005 Feb 22
0
Question about NA's
Hi, i got a little question about the NA's in vectors and matrices. When I want to do some operations on a matrix with some NA's it is possible to stripp them before the computation proceed (by na.rm=TRUE). But how can I stripp NA's when I want to proceed a 'if', 'for' or 'while' string? Because when I don't stripp them I always reveive the message
2010 Mar 25
1
Error using Rcpp
Hi, Im not sure if this is the right place to post this. I am using Xubuntu Karmic Koala and am trying to use the Rcpp package. I am testing it using a simple code that takes in a vector and adds 1 to each element: #include <Rcpp.h> // This file takes in a vector and adds one to each entry RcppExport SEXP addone(SEXP vec){ // create a local copy of vec Rcpp::NumericVector
2005 Jun 15
0
(PR#7942) extra spaces before imag part when printing complex numbers
Prof Brian Ripley wrote: > This is intentional: it aligns the numbers. E.g. > > >options(width=12) > >print(c(1+1i, 1-10i, 1+100i)) > [1] 1+ 1i > [2] 1- 10i > [3] 1+100i > > Neat, eh? > > What made you think this was a bug? Ah ok, I've misunderstood this feature probably perhaps because, at first sight, I found the display looks "strange"
2008 Jun 24
2
Debugging
Hi! It's indeed better to open a new thread for this. So, here's my test session: $ qemu -fda extlinux.144 -s -S Then in another terminal: $ gdb extlinux.elf (gdb) set architecture i8086 (gdb) target remote localhost:1234 Remote debugging using localhost:1234 0x0000fff0 in ?? () at localboot.inc:68 68 jmp kaboom ; If we returned, oh boy... How does "jmp kaboom" get
2007 Apr 18
0
[RFC/PATCH PV_OPS X86_64 12/17] paravirt_ops - interrupt/exception changes
plain text document attachment (xx-paravirt-irqs.patch) Interrupt updates for paravirt ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/ia32/ia32entry.S =================================================================== --- clean-start.orig/arch/x86_64/ia32/ia32entry.S +++
2007 Apr 18
0
[RFC/PATCH PV_OPS X86_64 12/17] paravirt_ops - interrupt/exception changes
plain text document attachment (xx-paravirt-irqs.patch) Interrupt updates for paravirt ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/ia32/ia32entry.S =================================================================== --- clean-start.orig/arch/x86_64/ia32/ia32entry.S +++
2017 Apr 25
1
[LLD] Linking static library does not resolve symbols as gold/ld
Hi Martin, Thank you for sending the script. I can reproduce the issue with it. It looks like the program crashes when it tries to call std::vector<sometype>'s ctor from a static initializer. I don't fully understand what is causing the issue yet, but here are my observations. - Since you are creating a temporary object file using `ld.gold -r`, your object file contains multiple
2017 Mar 23
2
[LLD] Linking static library does not resolve symbols as gold/ld
Hi Martin, It's hard to tell what is wrong only with the information. If that is an open-source program, can you give me a link to that so that I can try? If that's a proprietary software you cannot share with me, you might want to produce small reproducible test case. On Thu, Mar 23, 2017 at 1:10 AM, Martin Richtarsky <s at martinien.de> wrote: > Hi Rui, > > fyi I'm
2009 Feb 19
2
[LLVMdev] -fPIC warning on every compile on Cygwin
On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > Hi, > > > > > > I partly built LLVM on Cygwin yesterday and it was fine
2009 Feb 21
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:
2009 Feb 19
0
[LLVMdev] -fPIC warning on every compile on Cygwin
Aaron Gray wrote: > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning