search for: longly

Before I file a bug, I thought I'd check to make sure something hasn't changed. Stacker used to work in 1.2, now it fails on six tests. All six tests pertain to use of the SetLT, SetGT, SetLE, and SetGE SetCondInst. In my test programs they all fail, regardless of the values. The *only* thing I've done to Stacker is to change the base type involved in the comparison from int to long.

Hi, I have installed openSuse 11.1, which uses wine 1.1.11. I had already used wine with openSuse 10.3 which, I think, had the version 1.0. I have a dictionary for windows which doesn't work well in wine 1.1.11 but it worked with a small problem, but not so big, in 1.0. As in all dictionaries, the explanation of a word is shown in a text box. When the explanation is too long the text box

Hello, I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have our own gcc compiler that we build with crosstools-ng (based on gcc 6.3.0) and I set my environment like this: CC=armv7a-plex-linux-gnueabihf-gcc CXX=armv7a-plex-linux-gnueabihf-g++ CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16 --sysroot=<path> CXXFLAGS=-fPIC -DPIC

At first glance, it looks like long double functions (such as fabsl and friends) are missing from your sysroot's <math.h>. Does your target support long double at all? -Dimitry > On 6 Feb 2018, at 09:51, Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > > I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have

Hello Dimitry and thanks for your answer. I am pretty sure it does indeed support long double. It's configured with vfpv3-d16 - but I noticed that c++config.h in gcc has _GLIBCXX__HAS_FABSL and friends are undefined. I think I need to look deeper at the configuration of our toolchain. long double support is required in libc++ then I gather? -- Tobias On Tue, Feb 6, 2018 at 11:47 AM,

please add the following diffs to the vorbis/vq dir. - include files changed so things actually compile in new scheme - _ogg_...alloc cleanups caught a half-dozen typos or so - minor Makefile touchup. (stuff is still not tested, but this will compile at least) Would someone with cvs write access commit them for me please? Erik diffs: ------------------------ diff -bBu2r vorbis/vq/Makefile

Hello, I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have our own gcc compiler that we build with crosstools-ng (based on gcc 6.3.0) and I set my environment like this: CC=armv7a-plex-linux-gnueabihf-gcc CXX=armv7a-plex-linux-gnueabihf-g++ CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16 --sysroot=<path> CXXFLAGS=-fPIC -DPIC

Dear users, I am attempting to plot an ols() call from the Design package, by following the procedure explained by Harald Baayen in his 2008 book 'Analyzing linguistic data. A practical introduction to statistics using R', page 175-181. I've attached my data to this e-mail (I hope it's small enough that that's ok). First I paste all the commands I ran, followed by the

Hi R users, Wonder if somebody could give me help on how to reshape this type of data: ----------------------------------------------------------------------------------------------------------------------- Date:10.09.19 Time:21:39:05 Lat:N62.37.18 Long:E018.07.32 0000-0010 | 28| 28 0010-0020| 302| 302 0020-0030| 42| 42 0030-0040| 2| 2 0040-0050| 1| 1 0060-0070| 1| 1

Hi everybody, it was requested that kramdown (a Markdown parser in Ruby, see <http://kramdown.rubyforge.org>) supports the lazy syntax of Markdown. So I sat down, thought about it, skimmed through the Markdown ML on issues regarding lazy indentation as done with Markdown and now I have some rough idea on how to do this in kramdown. First: I'd like to say that there is no way to satisfy

Hi Xiantao, Some more nit-picking, though some of this is a bit more important to fixup. Cheers, Jes > +typedef struct thash_data { Urgh! argh! Please avoid typedefs unless you really need them, see Chapter 5 of Documentation/CodingStyle for details. > diff --git a/include/asm-ia64/kvm_host.h b/include/asm-ia64/kvm_host.h > new file mode 100644 > index 0000000..522bde0 > ---

Hi Xiantao, Some more nit-picking, though some of this is a bit more important to fixup. Cheers, Jes > +typedef struct thash_data { Urgh! argh! Please avoid typedefs unless you really need them, see Chapter 5 of Documentation/CodingStyle for details. > diff --git a/include/asm-ia64/kvm_host.h b/include/asm-ia64/kvm_host.h > new file mode 100644 > index 0000000..522bde0 > ---

Hi all, I have the folloing data table %%%%%%%%%%%%%%%%%% Type BATCH RESPONSE SHORT A 22 SHORT A 3 SHORT A 16 SHORT A 14 SHORT A 8 SHORT A 27 SHORT A 11 SHORT A 17 SHORT B 12 SHORT B 17 SHORT B 11 SHORT B 10 SHORT B 16 SHORT B 18 SHORT B 15 SHORT B 13 SHORT B 9 SHORT B 20 SHORT C 4 SHORT C 16 SHORT C 32 SHORT C 11 SHORT C 9 SHORT C 25 SHORT C 27 SHORT C 12 SHORT C 26 SHORT C 7 SHORT C 14 LONG A

Hi Nicholas, I love your patch! Yet something to improve: [auto build test ERROR on powerpc/next] [also build test ERROR on tip/locking/core v5.8-rc3 next-20200702] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use as documented in https://git-scm.com/docs/git-format-patch] url:

This patch moves lguest.c one level bellow, and enhances it with the ability to kick off 64 binaries. It would be much easier to just ifdef functions, but I have x86_64 machines loading 32-bit kernels as a longer goal, and that's why the patch features the load_elf_header() function. Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> -- Glauber de Oliveira Costa Red Hat Inc.

This patch moves lguest.c one level bellow, and enhances it with the ability to kick off 64 binaries. It would be much easier to just ifdef functions, but I have x86_64 machines loading 32-bit kernels as a longer goal, and that's why the patch features the load_elf_header() function. Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> -- Glauber de Oliveira Costa Red Hat Inc.

Hi. R-exts, section 1.7, discusses the passing of long long integers between R and C. I want to use unsigned long long integers, but I only need them inside a C function. I have a function that maps the nonnegative integers to the positive integers. The function is defined by a delicate recursive algorithm that is exact for integer arithmetic, but wildly incorrect for doubles. The function

Each of these drivers has a copy of the same trivial helper function to convert the pointer argument and then call the native ioctl handler. We now have a generic implementation of that, so use it. Acked-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com> Reviewed-by: Jason Gunthorpe <jgg at mellanox.com>

Each of these drivers has a copy of the same trivial helper function to convert the pointer argument and then call the native ioctl handler. We now have a generic implementation of that, so use it. Acked-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com> Reviewed-by: Jason Gunthorpe <jgg at mellanox.com>

Hello, In Rcpp we'd like to do something useful for types such as long long and unsigned long long. For example, supporting our usual wrap construct. We'd like to be able to "wrap" a long long, or perhaps a std::vector<long long> so that it is returned to the R side in something meaningful (we are considering several options like loosing some precision and returning