similar to: C macros and Makevars/package building

Hi This is a question prompted by the mac version of R, but as I see it, it should have broader interest. These days the CRAN Mac binary per default compiles every package for two architectures. First i386 and then ppc. In between the two compilation runs, any object files in pkgname/src is removed. This cleanup is necessary since otherwise Make would not recompile the object files

Hello, For not too regular users of R, preparing the data is somehow a burden. Comming from iMacro in FireFox I get a badly designed csv, which I need to put into a daily R script. The data looks like that (e.g.): 22 Results,"35 Results","39 Results","2 Results","7 Results","23 Results","42 Results","36 Results","22

Hello, I'm enabling clang LTO to improve code size of Uefi standard (http://www.uefi.org/) firmware (https://github.com/tianocore/edk2), which is mostly C code. My project is in https://github.com/shijunjing/edk2 branch llvm : https://github.com/shijunjing/edk2/tree/llvm. I find my most firmware modules work well after enable LTO, but some X64 modules will not run (e.g. hang with CPU

Alright thank you all for your help and information and sry for describing it as a bug. For a "fast" workaround I simple use llvm-gcc with -O0, modify the endian information within the ll file and use opt to optimize the code. That way also the debugging information is not removed and everything works atm fine for a non-trivial application. Later I'll also modify the front-end to

On Thu, Apr 02, 2015 at 03:17:13PM +0200, Greg Kurz wrote: > This patch brings cross-endian support to vhost when used to implement > legacy virtio devices. Since it is a relatively rare situation, the feature > availability is controlled by a kernel config option (not set by default). > > If cross-endian support is compiled in, vhost abvertises a new feature > to be negotiated

On Thu, Apr 02, 2015 at 03:17:13PM +0200, Greg Kurz wrote: > This patch brings cross-endian support to vhost when used to implement > legacy virtio devices. Since it is a relatively rare situation, the feature > availability is controlled by a kernel config option (not set by default). > > If cross-endian support is compiled in, vhost abvertises a new feature > to be negotiated

Hi all, I'm trying to install iMacros (http://www.iopus.com/imacros/ - download http://www.iopus.com/download) on my Ubuntu Dapper box running Wine 0.9.9. iMacros is a webbrowser Macro/Automation/Testing application that I haven't been able to find an equivalent for in the *NIX world. If anyone knows of something I can run native, please, please, please let me know about it!! :-)

Stripf, Timo wrote: > I thought the LLVM IR is target independent Yes. and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. No. > I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. LLVM IR contains a target-information line but is otherwise target

Hi Edwin, > FWIW here is another way to do it (which is approximately what ClamAV does currently) by introducing just one intrinsic: > declare i1 @llvm.is_bigendian() why is an intrinsic needed? It is easy to write a small LLVM IR function that computes this. For example: define i1 @is_big_endian() { %ip = alloca i16 store i16 1, i16* %ip %cp = bitcast i16* %ip to i8* %c =

I thought the LLVM IR is target independent and that "llvm-gcc -c -emit-llvm -O2" produces target independent code. I'm working on a back-end and use llvm-gcc to first generate the bc file. Afterwards I use llc including the new back-end to produce the assembler file. -Timo -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. It is a complete rework of my initial post. Patches 1 to 5 are preliminary work: we move the endianness check out of all memory accessors to separate functions. Patch 6 changes the semantics of the accessors so that they have explicit big endian support. Patch 7 brings the cross-endian

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. It is a complete rework of my initial post. Patches 1 to 5 are preliminary work: we move the endianness check out of all memory accessors to separate functions. Patch 6 changes the semantics of the accessors so that they have explicit big endian support. Patch 7 brings the cross-endian

I'm attempting to flac a 18GB raw file, and as per 1328191 I compiled CVS, when it gets to 4GB it doesn't continue. I've tried stracing and get no output after a certain point. I also have tried oggflac and it is no different. I configured with no options or special CFLAGS and this is on a x86 machine. Is there anything special I need to do to get this to work? I have also tried with

On 10/03/2011 09:36 PM, Villmow, Micah wrote: > One of the projects I am working on with others is to make LLVM-IR endian agnostic. > > > > So, I am sending out this proposal for feedback to the LLVM community. I’ve attached > > pretty version of the proposal in PDF format and pasted a 80-column safe text version > > below. > > > > A second smaller

Hi, This series allows QEMU to use vhost with legacy virtio devices when host and target don't have the same endianness. Only network devices are covered for the moment. I had already posted a series some monthes ago but it never got reviewed. Moreover, the underlying kernel support was entirely re-written and is still waiting to be applied by Michael. I hence post as RFC. The corresponding

Hi, This series allows QEMU to use vhost with legacy virtio devices when host and target don't have the same endianness. Only network devices are covered for the moment. I had already posted a series some monthes ago but it never got reviewed. Moreover, the underlying kernel support was entirely re-written and is still waiting to be applied by Michael. I hence post as RFC. The corresponding

Hi, I asked some days ago how to guess the o.s. the machine is running. I found that it is stored in a variable called R_PLATFORM. Now I need a full list of all the values this variable can have because I need to set an option depending on the endianness of the platform in which we are compiling the package. Anyone can help me? Thanks, Virgilio Gómez Rubio Dpto. Estadística e

Hello, I just tried configuring R to use architecture-dependent subdirs $ r_arch=x86_64 ./configure --prefix=/u/smat/konis/testdir on a Debain Squeeze box $ uname -a Linux smapc007 2.6.32-5-686 #1 SMP Sat Sep 18 02:14:45 UTC 2010 i686 GNU/Linux After building and installing, the Rconfig.h ended up in .../lib/R/include/x86_64 but R.h still includes it as #include <Rconfig.h>

I am just trying to adjust one of my packages so the C code builds in Windows. This is code that has been around for a long time, and I'm am only a casual reader of C, so it has had the "if it is not broken don't touch it" approach for many years. The section 1.2.1 "Using Makevars" of "Writing R extensions" starts: "Sometimes writing your own

Hi all, Recently, when compiling R packages containing C code, I've started getting the following error: * installing to library ?/Users/hadley/R? * installing *source* package ?appdirs? ... ** Creating default NAMESPACE file ** libs *** arch - i386 gcc -arch i386 -std=gnu99 -I/Library/Frameworks/R.framework/Resources/include -I/Library/Frameworks/R.framework/Resources/include/i386 -DNDEBUG