similar to: [LLVMdev] getting error while running tblgen

Thanks for your advice. I am not sure that I understood your comment "If you need something, there should be a __builtin that corresponds to the intrinsic." Is that a better way to define an intrinsic function in C? How do you do it? I am actually trying to add several intrinsic functions for my target machine so I am looking for a simple and workable way of doing it. Thanks again.

On Dec 29, 2009, at 5:50 AM, fima rabin wrote: > I am trying to compile this little C-program: > ================= > typedef double v2f64 __attribute__((ext_vector_type(2))); > > int sse2_cmp_sd(v2f64, v2f64, char ) asm("llvm.x86.sse2.cmp.sd"); We used to support this, but there are problems with it. I actually just went to go implement this again, which

On Jan 6, 2010, at 1:12 PM, fima rabin wrote: > I am trying to compile a little intrinsic function for my machine. Here is a dump from clang-cc with --emit-llvm option: > ===================== > > ; ModuleID = 'foo.c' > target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32" >

On Mon, Feb 05, 2007 at 12:28:56PM -0800, Chris Lattner wrote: > On Mon, 5 Feb 2007, Dan Gohman wrote: > > > LLVM knows what all the types of the intrinsic functions are; I thought, > > why are users (including llvm-gcc...) required to duplicate all this > > information in order to use them? I mean in order to call > > getOrInsertFunction to get declarations for

I am trying to compile a little intrinsic function for my machine. Here is a dump from clang-cc with --emit-llvm option: ===================== ; ModuleID = 'foo.c' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32" target triple = "i386-pc-linux-gnu" @main.i = internal global i32

I've written a Smalltalk application which starts R on another machine and then communicates with it via sockets. The functions involved are: slaveStart <- function(masterHost, masterPort){ inPort <- availablePort() sendSocket(as.character(inPort), masterHost, masterPort) socketSlave(inPort) } socketSlave <- function(inPort){ ## listens on inPort.

Mark Knecht wrote: > On Sat, Mar 8, 2008 at 11:28 AM, Dan Kegel <dank at kegel.com> wrote: > > > On Sat, Mar 8, 2008 at 11:22 AM, Mark Knecht <markknecht at gmail.com> wrote: > > > > > Does this mean run it again but use +relay in the command line? > > > > > > > Yes. > > > > > > > > > If so could you give

Hi all, I am trying to build a cross compiler for Sparc on x386 host. I tried to run configure with configure --enable-targets=sparc or with configure --target=sparc but in both cases I got llvm compiler for x86 target. Is there a way to build a cross compiler for Sparc (or ARM)? Thanks. -- Fima Rabin -------------- next part -------------- An HTML attachment was

I am trying to compile this little C-program: ================= typedef double v2f64 __attribute__((ext_vector_type(2))); int sse2_cmp_sd(v2f64, v2f64, char ) asm("llvm.x86.sse2.cmp.sd"); int main() { static int i; static float x[10]; static float y[10]; v2f64 m1; v2f64 m2; int j; i = sse2_cmp_sd(m1,m2,'z'); ========================== I expected to

> Please start a thread on llvmdev about this functionality, and outline what other intrinsics will have to change to add non-8-bit byte support. Well, memset is the only we have seen so far (our back-end is ~50% finished for an initial release). We have our own front-end as well (we are currently not using the clang front-end), and currently don't use many llvm intrinsics (only

I have defined the intrinsic as * def int_loop: Intrinsic<[],[llvm_i8_ty, llvm_empty_ty],[]>;* and also got the Codegen backend support in Instructioninfo.td file. Then created a .ll file to test it. The .ll file is like this *declare void @llvm.loop(i8, label)define void @fn() nounwind readnone {entry: ..... ..... call void @llvm.loop(i8 10, label %entry) ret void}* But

I need some guidance on what is the best way to automate R I am aware of Rterm. First question: Is it true that R is not currently OLE accessible under Windows 2000? Second question: Is there an R command that echoes all R Console results to a run log system file? My first attempt to write a run log file is the example from the R Data Inport/Export documentation. > zz<-

Regards. I'm a beginner in programing, so I have a basic question for you. If someone could help me please.. I want to create a function, which will be able to export files from excel. I tried with a <- read.csv(file, sep =",", as.is = TRUE, row.names = 1, header = TRUE), .. but instead of numbers, it gives me strings for example: "299,311". I can handle this string

FYI, The CRC64 intrinsics were renamed to CRC32 since there is no such thing. See below for details. Chad On May 26, 2011, at 4:13 PM, Chad Rosier wrote: > Author: mcrosier > Date: Thu May 26 18:13:19 2011 > New Revision: 132163 > > URL: http://llvm.org/viewvc/llvm-project?rev=132163&view=rev > Log: > Renamed llvm.x86.sse42.crc32 intrinsics; crc64 doesn't exist.

Eribium, a content managing system built with rails has been released completely free under the MIT License. http://www.eribium.org/eribium/?p=21 You can find a demo here: http://alexmaccaw.no-ip.info:3000/admin (user and pass are ''demo''). Some of the features include: * Completely Unobtrusive Javascript. * Liquid View, works with pretty much any screen resolution.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I have come across a problem after upgrading from 1.0.rc17 to 1.0.13 (debian builds 1.0.13 is from etch-backports). I initially upgraded as 1.0.rc17 isn't compiled with regex support, so vacation messages that were uploaded via horde were being rejected. (Everything else was working fine, just messages that required regex functions

Hi all, I did my first bug report in a while. Unfortunately the good folks at wineHQ.org didn't like it much because Gentoo by default stripped out much of the backtrace info. I've recompiled Wine with more backtrace capabilities in it and am wondering what's considered good enough. Below are two backtraces. They may or may not be exactly the same failure but they both come from

On Mon, 5 Feb 2007, Dan Gohman wrote: > LLVM knows what all the types of the intrinsic functions are; I thought, > why are users (including llvm-gcc...) required to duplicate all this > information in order to use them? I mean in order to call > getOrInsertFunction to get declarations for them. That is an excellent question! :) In the bad old days, we used to allow intrinsics

LLVM knows what all the types of the intrinsic functions are; I thought, why are users (including llvm-gcc...) required to duplicate all this information in order to use them? I mean in order to call getOrInsertFunction to get declarations for them. So I wrote this patch, which allows all this code to be generated automatically. Is this a good approach? Dan -- Dan Gohman, Cray Inc. <djg at

Hi Chandler > Key things I'm currently thinking about after a brief brainstorm: > - Post-commit triggers need to be ported and kept useful > - Special attention to ensure that the existing code review / commit email > system continues to be effective > - Provide individual git repositories for each LLVM project, along with meta > repositories that use submodules to layout