search for: ratifi

Dear Everybody: I'm doing my usual "how does that work in R" thing with some Stata projects. I find a gross gap between the Stata and R in Cox PH models, and I hope you can give me some pointers about what goes wrong. I'm getting signals from R/Survival that the model just can't be estimated, but Stata spits out numbers just fine. I wonder if I should specify initial

...of standard extensions (e.g. floating point, atomics, etc). New standard extensions are developed through RISC-V Foundation working groups. The specifications for such extensions (e.g. vector and bit manipulation) are publicly available, but are still in flux and won't be finalised until "ratified" by the Foundation. This RFC considers how we should handle review and merging of support for in-development standard extensions, with a view to maximising collaboration and reduce duplicate effort. The summarised proposal is that patches for in-development standard extensions should be enc...

On Wed, 22 Jan 2020 at 19:55, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Jan 21, 2020, at 5:00 AM, Alex Bradbury <asb at lowrisc.org> wrote: > >> This all makes sense to me. > > > > That's correct, thanks for the feedback. > > > > I do like the idea from James of having the compiler always spit out a > > note

From: Aaron Conole <aconole at bytheb.org> The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by virtio_cread16 will never exceed the in...

From: Aaron Conole <aconole at bytheb.org> The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by virtio_cread16 will never exceed the in...

On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> wrote: > **** Introduction **** > Lately, Khronos has ratified a new provisional specification which is called SPIR. > This specification standardizes an intermediate representation for the OpenCL kernel language. > It is based on LLVM infrastructure and this is why I am sending this mail to the LLVM mailing list. > Khronos members would like to i...

...lists.llvm.org> wrote: > > I believe code should be committed to LLVM when it is of sufficient > > quality, when it can be shown to benefit the LLVM user or developer > > communities, and when there is someone willing to support it. All of these can > > be true even for unratified standard RISC-V extensions, with a caveat on > > "support”. > > +1 > > > # Proposal > > > > Although we want to discourage downstream reliance on unratified extensions, > > there doesn't seem to be a strong motivation for requiring a custom LLVM bui...

...about the way inheritance works (or doesn't work) from the Windows ACL editor, but that would make this a very long message... I can't wait until Samba gets a proper Windows ACL implementation (through the VFS?) and we get done with this POSIX ACL thing (which by the way is not even a ratified standard...). It would be great to hear some comment on this from the members of the list or any of the samba developers who can spare a minute. A big thank you to all of the Samba team!

...mdev at cs.uiuc.edu > Subject: Re: [LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL > Kernel Language > > On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> > wrote: > > > **** Introduction **** > > Lately, Khronos has ratified a new provisional specification which is > called SPIR. > > This specification standardizes an intermediate representation for > the OpenCL kernel language. > > It is based on LLVM infrastructure and this is why I am sending this > mail to the LLVM mailing list. > > Khr...

The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by virtio_cread16 will never exceed the in...

The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by virtio_cread16 will never exceed the in...

Hello, will the next update of CentOS 6 (6.10) have TLSv1.3 support? Thanks, Walter

Hello, Background: We (the Portable Native Client team) would like to continue upstreaming our LLVM modifications which contain support for Software Fault Isolation (SFI) as required for sandboxing programs to run under Native Client. Since the "total patch size" is quite big, we are splitting the effort to manageable chunks that can be committed, tested and reviewed separately as

Following on from my previous missive - now apparently resolved :D I now have another problem. This time with Sage Line50 Ver11. It appears to have installed OK and seems to link to the network share drive (G:), however it will not allow me (or anyone else) to log in. If I use any good username, it comes back with "invalid password", even for users with no password. If I use any

On Sun, Apr 06, 2014 at 09:32:09PM +0000, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger <nab at linux-iscsi.org> > > This patch updates virtscsi_probe() to setup necessary Scsi_Host > level protection resources. (currently hardcoded to 1) > > It changes virtscsi_add_cmd() to attach outgoing / incoming > protection SGLs preceeding the data payload, and is

On Sun, Apr 06, 2014 at 09:32:09PM +0000, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger <nab at linux-iscsi.org> > > This patch updates virtscsi_probe() to setup necessary Scsi_Host > level protection resources. (currently hardcoded to 1) > > It changes virtscsi_add_cmd() to attach outgoing / incoming > protection SGLs preceeding the data payload, and is

Greetings All, I am sending this mail on behalf of the OpenCL Khronos members. **** Introduction **** Lately, Khronos has ratified a new provisional specification which is called SPIR. This specification standardizes an intermediate representation for the OpenCL kernel language. It is based on LLVM infrastructure and this is why I am sending this mail to the LLVM mailing list. Khronos members would like to initiate a revie...

All, We have our first CL ready and waiting, but haven't heard from the community. Are there issues or suggestions we should understand a priori? Cheers, David On Tue, Jan 15, 2013 at 3:59 PM, David Sehr <sehr at google.com> wrote: > Hello, > > Background: > We (the Portable Native Client team) would like to continue upstreaming > our LLVM modifications which

On Mon, Apr 07, 2014 at 01:56:59AM -0700, Nicholas A. Bellinger wrote: > On Mon, 2014-04-07 at 11:45 +0300, Michael S. Tsirkin wrote: > > On Sun, Apr 06, 2014 at 09:32:09PM +0000, Nicholas A. Bellinger wrote: > > > From: Nicholas Bellinger <nab at linux-iscsi.org> > > > > > > This patch updates virtscsi_probe() to setup necessary Scsi_Host > > >

On Mon, Apr 07, 2014 at 01:56:59AM -0700, Nicholas A. Bellinger wrote: > On Mon, 2014-04-07 at 11:45 +0300, Michael S. Tsirkin wrote: > > On Sun, Apr 06, 2014 at 09:32:09PM +0000, Nicholas A. Bellinger wrote: > > > From: Nicholas Bellinger <nab at linux-iscsi.org> > > > > > > This patch updates virtscsi_probe() to setup necessary Scsi_Host > > >