search for: quicly

Prof Brian Ripley wrote: > 'library' in R has a different meaning: I've altered the subject to be > more accurate 'libR'. > > This is what R CMD SHLIB is for: it does all this for you in a portable way. > > But if you want to DIY, you can use R CMD config to find out the > appropriate linker incantation. Thank you for the clarification. I do not insist on

LLVM Developers, The compiler teams at the Qualcomm Innovation Center are hiring. In summary, we are doing interesting things with LLVM; come join us! I have included a more detailed description below. If you are interested, please contact me at adasgupt at quicinc.com -Anshu --- Opportunities at Qualcomm Innovation Center, Inc. Compiler Technologies Mobile devices are increasingly supporting

Hai, You can very easy upgrade to 3.5.12 on Jessie. Add sid to your sources.list, or better in : /etc/apt/sources.list.d/debian-sid.list Only the deb-src line is needed. Now apt-get update # install dependecies. apt-get build-dep squid # get and build source. apt-get source squid -b if you missing something, get that package first, build it, install it and do above again. !! thing to

Mike, The accounting department here also runs Quickbooks. It also wouldn't run as a standard Domain User. On our old Windows PDC, the Accountant had to be setup as at least a Power User to be able to use the software. While I haven't had much of a chance to dig into it lately, it might just have something to do with file permissions on the Quickbooks directory. Although,

I am new to LLVM but have perused the code alongside using llvm-gcc and CLANG to build ARM EABI objects. Based on this superficial analysis it appears that LLVM currently does not support the ARM Exception Handling ABI (as defined under the EABI). Can anyone comment on whether plans are in place to remedy this? I did see the discussion regarding work on the MC for ARM. Will this work include

On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: >>> If you want to compare it with >>> something that would be TCP or QUIC. The fundamental difference between >>> virtio-vsock and e.g. TCP is that TCP operates in a packet loss environment. >>> So they are using timers for reliability, and receiver is always free to >>> discard any unacked data.

On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: >>> If you want to compare it with >>> something that would be TCP or QUIC. The fundamental difference between >>> virtio-vsock and e.g. TCP is that TCP operates in a packet loss environment. >>> So they are using timers for reliability, and receiver is always free to >>> discard any unacked data.

[Please CC me on replies, as I am not subscribed.] Dear R folks, Accessing the *R Developer Page* [1], the browser (Firefox) shows an HTTPS warning. The reason is the embedded Google logo. > Gemischte (unsichere) Anzeige-Inhalte von "http://www.google.com/logos/Logo_40wht.gif" werden auf einer sicheren Seite geladen Could you change that to an HTTPS link please? ``` $ curl -I

Hi, On the hexagon target, I have written a following combiner pattern. ********************************************* def: Pat<(i64 (or (i64 (shl (i64 (extloadi32 (i32 (add IntRegs:$src1, s11_2ExtPred:$offset1)))), (i32 32))), (i64 (zextloadi32 ADDRriS11_2:$src2)))), (i64 (COMBINE_rr

> Are these two backends ABI compatible? They should be, where there's overlap. AArch64 doesn't have any MachO support at the moment. ARM64 does have ELF support (obviously with less testing than AArch64's). Any ABI discrepancy would be considered a bug. > If I have a toolchain setup for the existing aarch64-linux-gnu triple, could > I try the new backend and still have

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

On 2018/11/29 ??10:00, Michael S. Tsirkin wrote: > On Thu, Nov 15, 2018 at 04:24:38PM +0800, Jason Wang wrote: >> On 2018/11/15 ??3:04, Michael S. Tsirkin wrote: >>> On Thu, Nov 15, 2018 at 11:56:03AM +0800, jiangyiwen wrote: >>>> Hi Stefan, Michael, Jason and everyone, >>>> >>>> Several days ago, I discussed with jason about "Vsock over

On 2018/11/29 ??10:00, Michael S. Tsirkin wrote: > On Thu, Nov 15, 2018 at 04:24:38PM +0800, Jason Wang wrote: >> On 2018/11/15 ??3:04, Michael S. Tsirkin wrote: >>> On Thu, Nov 15, 2018 at 11:56:03AM +0800, jiangyiwen wrote: >>>> Hi Stefan, Michael, Jason and everyone, >>>> >>>> Several days ago, I discussed with jason about "Vsock over

Hello LLVM Devs, I am starting my PhD on Automatic Parallelization for DSP and want to play with some ARM NEON intrinsics for a start. I spent the last three days trying to compile a version of LLVM that would allow me to compile sources that contain these intrinsics, but with no success. In the process I found out that clang doesn't support NEON (as per

On Mon, Sep 27, 2010 at 8:50 AM, Dennis Taul <dtaul at codeaurora.org> wrote: > > I am new to LLVM but have perused the code alongside using llvm-gcc > and CLANG to build ARM EABI objects. > > Based on this superficial analysis it appears that LLVM currently does > not support the ARM Exception Handling ABI (as defined under the > EABI). > > Can anyone comment on

On Wed, Jul 11, 2018 at 6:58 PM, David Newall <openssh at davidnewall.com> wrote: > I remember, when Sun first released NFS they used UDP for transport because > "performance", and then, not so very long later, had to implement TCP > transport because "reliability". network reliability has changed quite a bit since the 80's. see eg QUIC

Hello! Four security issues were identified in nginx HTTP/3 implementation, which might allow an attacker that uses a specially crafted QUIC session to cause a worker process crash (CVE-2024-31079, CVE-2024-32760, CVE-2024-35200), worker process memory disclosure on systems with MTU larger than 4096 bytes (CVE-2024-34161), or might have potential other impact (CVE-2024-31079, CVE-2024-32760).

Hello! В реализации HTTP/3 в nginx были обнаружены четыре проблемы, которые позволяют атакующему с помощью специально созданной QUIC-сессии вызвать падение рабочего процесса (CVE-2024-31079, CVE-2024-32760, CVE-2024-35200), отправку клиенту части содержимого памяти рабочего процесса на системах с MTU больше 4096 байт (CVE-2024-34161), а также потенциально могут иметь другие последствия

Changes with nginx 1.27.4 05 Feb 2025 *) Security: insufficient check in virtual servers handling with TLSv1.3 SNI allowed to reuse SSL sessions in a different virtual server, to bypass client SSL certificates verification (CVE-2025-23419). *) Feature: the "ssl_object_cache_inheritable", "ssl_certificate_cache",