similar to: [6.0.0 Release] Release notes nag email

> I would like a command line option to disable this optimization. That way tests can still verify that EVEX instructions came out of isel by using -show-mc-encoding. I think that keeping tests compatibility is not a reason for an additional “llc” flag. We check encoding in test/MC/X86 dir. Is there any option to report-out from llc in non-debug mode? It should be an option to control

Hal, that’s a good point. There are more manually-maintained tables in the X86 backend that should probably be tablegened: the memory-folding tables and ReplaceableInstrs, to name a couple. If you have ideas on how to get these auto-generated, please let us know. From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Hal Finkel via llvm-dev Sent: Wednesday, November 23, 2016

I would like a command line option to disable this optimization. That way tests can still verify that EVEX instructions came out of isel by using -show-mc-encoding. On Wed, Nov 23, 2016 at 5:01 AM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > ------------------------------ > > *From: *"Gadi via llvm-dev Haber" <llvm-dev at lists.llvm.org> >

Dear guRus: I am using lmer for a mixed model that includes a random intercept for a set of effects that have the same distribution, Normal(0, sig2b). This set of effects is of variable size, so I am using an as.formula statement to create the formula for lmer. For example, if the set of random effects has dimension 8, then the lmer call is: Zs<-

Hi All. This is an RFC for a proposed target specific X86 optimization for reducing code size in the encoding of AVX-512 instructions when possible. When the AVX512F instruction set was introduced in X86 it included additional 32 registers of 512bit size each ZMM0 - ZMM31, as well as additional 16 XMM registers XMM16-XMM31 and 16 YMM registers YMM16-YMM31. In order to encode the new registers of

Hi, I am trying to compare the loop vectorizers effectiveness for different targets relative to each other. That way, I am hoping to find loops that are not vectorized - but could be - on my target by finding other targets doing this successfully. With some luck, there might be something in the Target files that could be fixed with improved vectorization as a result... I would like to do

Hello, I'm running my rsynce server on Win2k3 Server. One client under Linux and another on Win2k3 Server. The problem is not really OS related though. My Server 2k3 client command is: C:\Progra~1\cwRsync\bin\rsync -rtv --ignore-errors --stats --delete --delete-during --delete-excluded --link-dest=/cygdrive/d/previous/c/backup.1 --files-from=files-from.txt --exclude-from=exclude-from.txt

Although I made sure that vim-enhanced.i386 is installed, pressing : then upArrow does not show me the last command that I've typed. Might I still be using vim-minimal erroneously? How to fix that? I don't see any mention of this in google or the past few months of fine archives. Thanks. [gadi at mercury ~]$ uname -a Linux mercury 2.6.18-194.3.1.el5PAE #1 SMP Thu May 13 13:48:44 EDT 2010

... to fix a problem with PostgreSQL reconnect after connection loss & put test coverage in place to keep it working in the future. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/EecNy-qyKwgJ. To post to this group, send email to

Hi, I am not sure how to fix the following error. LGD <- c(11.6, 12.3, 15.8, 33.1, 43.5, 51.3, 67.3, 84.9) cor (x=(file [1:47231,3:10]), y= rep (LGD, 47231), method = "pearson") Error in cor(x = (file[1:47231, 3:10]), y = rep(LGD, 47231), method = "pearson") : incompatible dimensions > sessionInfo() R version 2.13.0 (2011-04-13)

So that I can know there is test coverage on this in the Rails core, and I won''t have to maintain a private monkey-patch indefinitely, fixing it again every time it''s broken in a new and different way up-stream, I''m hoping to get this pull request accepted some day... ... or rejected in an informative manner, if that''s more appropriate.

Hello all, I was able to create R packages under windows XP in the past using the dynamic NAG C library for windows XP (Mark 6). Recently, I changed computers and I am now using the static NAG C library for windows XP (Mark 7) to create a simple R package (called "test") which simply returns random numbers simulated using repetitive calls to a NAG C routine (uniform random

On 13 March 2018 at 16:51, Ed Maste <emaste at freebsd.org> wrote: > On 7 February 2018 at 01:20, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I've landed the patch in r324449. > > To confirm, this change *did not* make it into 6.0.0, correct? I'm > looking at adding the external thunk for FreeBSD now, and we have > 6.0.0 in

On 7 February 2018 at 01:20, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I've landed the patch in r324449. To confirm, this change *did not* make it into 6.0.0, correct? I'm looking at adding the external thunk for FreeBSD now, and we have 6.0.0 in HEAD. Assuming that future Clang releases (major, and updates) will all use __x86_indirect_thunk_r11 we

On Thu, 11 Nov 2004 11:19:25 -0800, "Romain Neugebauer" <romain at berkeley.edu> wrote : >Dear Duncan Murdoch, > >I just posted the following message to the R-help mailing list in >response to your email of October 29th (see below). Unfortunately it >looks like my new message was not correctly posted, i.e. it does not >appear as a reply to yours but as a new

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

http://prereleases.llvm.org/ On Wed, Jan 24, 2018 at 1:08 PM, Nat! via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On 17.01.2018 18:53, Hans Wennborg via llvm-dev wrote: > >> Dear testers, >> >> Start your engines; 6.0.0-rc1 was just tagged. >> >> I know there are still open blockers and it's early in the process in >> a way, but

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

I am pleased to announce that LLVM 6 is now available. Get it here: https://llvm.org/releases/download.html#6.0.0 This release is the result of the community's work over the past six months, including: retpoline Spectre variant 2 mitigation, significantly improved CodeView debug info for Windows, GlobalISel by default for AArch64 at -O0, improved scheduling on several x86