similar to: Q aq fhc 8,-,,,8,c,c, cvv gz vc ccc

(Let's keep the discussion on-list -- I've added back R-devel.) On 2017-04-12 16:39, Ulrich Windl wrote: >>>> Henric Winell <nilsson.henric at gmail.com> schrieb am 12.04.2017 >>>> um 15:35 in > Nachricht <b66fe849-bb8d-f00d-87e5-553f866d57e0 at gmail.com>: >> On 2017-04-12 14:40, Ulrich Windl wrote: >> >>> The last line of the

>>>>> Rui Barradas <ruipbarradas at sapo.pt> >>>>> on Wed, 12 Apr 2017 17:07:45 +0100 writes: > Hello, Inline. > Em 12-04-2017 16:40, Henric Winell escreveu: >> (Let's keep the discussion on-list -- I've added back >> R-devel.) >> >> On 2017-04-12 16:39, Ulrich Windl wrote: >>

Hi there, I am glad to announce AQ-R 0.2 has been successfully built and is available via install.packages("aqr", repos="http://R-Forge.R-project.org"). The most important new feature is real-time messaging from within R. AQ-R 0.2 enables you to send and receive byte[] messages within R through a STOMP compliant messaging server, such as the ActiveQuant Master Server.

Hi there, I am glad to announce AQ-R 0.2 has been successfully built and is available via install.packages("aqr", repos="http://R-Forge.R-project.org"). The most important new feature is real-time messaging from within R. AQ-R 0.2 enables you to send and receive byte[] messages within R through a STOMP compliant messaging server, such as the ActiveQuant Master Server.

The last line of the example in droplevels' manual page seems to be incorrect to me. I think it should read: "table(droplevels(aq$Month))". Amazingly (I don't understand) both variants seem to produce the same result (R 3.3.3): --- > aq <- transform(airquality, Month = factor(Month, labels = month.abb[5:9])) > aq <- subset(aq, Month != "Jul") >

Hello, Inline. Em 12-04-2017 16:40, Henric Winell escreveu: > (Let's keep the discussion on-list -- I've added back R-devel.) > > On 2017-04-12 16:39, Ulrich Windl wrote: > >>>>> Henric Winell <nilsson.henric at gmail.com> schrieb am 12.04.2017 >>>>> um 15:35 in >> Nachricht <b66fe849-bb8d-f00d-87e5-553f866d57e0 at gmail.com>:

Does anybody know the purpose of test: projects/test-suite/SingleSource/UnitTests/SignlessTypes/ccc.c

But read the code and then answer the question. :) On 07/25/2012 06:19 PM, Gordon Keiser wrote: > From the comment at the top of the file: > > /* > * This file is used to the C calling conventions with signless > * LLVM. Integer arguments in this convention are promoted to at > * least a 32-bit size. Consequently signed values must be > * sign extended and unsigned

>From the comment at the top of the file: /* * This file is used to the C calling conventions with signless * LLVM. Integer arguments in this convention are promoted to at * least a 32-bit size. Consequently signed values must be * sign extended and unsigned values must be zero extended to * at least a 32-bit integer type. */ :-) -Gordon > -----Original Message----- > From:

Making a symlink to clang in the same directory as the GCC / binutils (I'll call it $ARM_BIN) called arm-none-linux-gnueabi-clang (and one with clang++ too) and another link in the $ARM_BIN/../lib directory to clang directory located under clang's lib (for includes) should be enough. Gordon Keiser Software Development Engineer Arxan Technologies gkeiser at arxan.com www.arxan.com 

Hi there, I'm using clang to cross compile for cortex-m3. I eventually managed to do so with clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-gnueabi source.cpp -c -mcpu=cortex-m3 I would like to understand what -ccc-gcc-name does exactly and how can I get ride of it? >From what I understand, it's needed by the driver in order to find the binutils for

Dear R-folks, I guess some of you are running R on Alpha/Linux boxes. I should be very happy, if they could tell us `success stories' as to the Subject. Compaq's ccc/cxx/fort for Alpha/Linux creates far better codes than gcc, and we want to recompile R with ccc/cxx/fort. Or, do we just miss existing good pointers for that? Thank you for your attention. Yoriaki Fujimori

On Mon, Jul 30, 2012 at 10:27 AM, Renato Golin <rengolin at systemcall.org> wrote: > On 30 July 2012 09:14, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> I'm sorry, I should have been more clear. I don't just want to get >> right of the option itself, I want not to >> have the need to a have a GCC cross-toolchain around. > >

On 30 July 2012 09:14, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > I'm sorry, I should have been more clear. I don't just want to get > right of the option itself, I want not to > have the need to a have a GCC cross-toolchain around. That requires a bit more than just compiling binutils. You'll need a working linker and a perfect interaction between

On Mon, Jul 30, 2012 at 3:51 AM, Gordon Keiser <gkeiser at arxan.com> wrote: > Making a symlink to clang in the same directory as the GCC / binutils (I'll call it $ARM_BIN) called > > arm-none-linux-gnueabi-clang (and one with clang++ too) > > and another link in the $ARM_BIN/../lib directory to clang directory located under clang's lib (for includes) > should be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When are you all going to make Samba compatible with CCC (Compaq Compiler)? I would really like to be able to compile it using CCC but I keep getting the errors listed below. I was wondering, could please point me in the right direction for a solution to this dilemma? ==================== ERROR MESSAGE ==================== Using FLAGS = -O -fast

On Thu, Jun 11, 2020 at 01:48:31PM +0200, Joerg Roedel wrote: > On Sat, May 23, 2020 at 09:59:24AM +0200, Borislav Petkov wrote: > > On Tue, Apr 28, 2020 at 05:16:57PM +0200, Joerg Roedel wrote: > > > + /* > > > + * Mark the per-cpu GHCBs as in-use to detect nested #VC exceptions. > > > + * There is no need for it to be atomic, because nothing is written to

On Tue, Jun 23, 2020 at 01:14:43PM +0200, Peter Zijlstra wrote: > On Tue, Jun 23, 2020 at 01:11:07PM +0200, Joerg Roedel wrote: > > The v3 patchset implements an unconditional shift of the #VC IST entry > > in the NMI handler, before it can trigger a #VC exception. > > Going by that other thread -- where you said that any memory access can > trigger a #VC, there just

On Tue, Jun 23, 2020 at 8:23 AM Andrew Cooper <andrew.cooper3 at citrix.com> wrote: > > On 23/06/2020 14:03, Peter Zijlstra wrote: > > On Tue, Jun 23, 2020 at 02:12:37PM +0200, Joerg Roedel wrote: > >> On Tue, Jun 23, 2020 at 01:50:14PM +0200, Peter Zijlstra wrote: > >>> If SNP is the sole reason #VC needs to be IST, then I'd strongly urge >

On 23/06/2020 12:30, Joerg Roedel wrote: > On Tue, Jun 23, 2020 at 01:07:06PM +0200, Peter Zijlstra wrote: >> On Tue, Apr 28, 2020 at 09:55:12AM +0200, Joerg Roedel wrote: >> So what happens if this #VC triggers on the first access to the #VC >> stack, because the malicious host has craftily mucked with only the #VC >> IST stack page? >> >> Or on the NMI IST