search for: quic

...did not fully understand the instructions in the document "R Extensions". (English is my second language.) A small example compiling a single .so would help greatly I think. My current Makefile that I put in src of a package skeleton looks like this to create the .so on Linux: all : QUIC.so OBJECTS = QUIC.o QUIC.so PKG_LIBS = @LAPACK_LIBS@ @BLAS_LIBS@ QUIC.o : QUIC.cpp g++ -O3 -DNDEBUG -Wall -fpic -pthread -shared -fno-omit-frame-pointer -ansi -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -c QUIC.cpp -o QUIC.o QUIC.so : QUIC.o g++ -std=gnu99 -shared -lm -llapack -lblas -L/usr/l...

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 sophisticated applications that only a few years ago were run exclusively on the desktop.  The mobile platforms of today are complex system on chips (SOCs) with m...

...gi > > I ask to update the distro to squid 3.4.14, the last stable version, > released in august. > > Rationale : > 1) various bugs and memory leaks fixed; > 2) security fix for CVE 2015 5400; > 3) support for Alternate-Protocol HTTP header. > > I need 3) to disable QUIC on youtube, otherwise squid3 cannot cache > videos. > > References : > https://packages.debian.org/jessie/squid3 > > ftp://ftp.fu-berlin.de/unix/www/squid/squid/squid-3.4-ChangeLog.txt > http://wiki.squid-cache.org/KnowledgeBase/Block QUIC protocol > >...

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 permissi...

...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 emitting the exception handling code/tables compliant to ARM's EH ABI? Thanks, -Dennis -- Dennis Taul | Qualcomm Innovation Center,Inc. (QuIC) 8041 Arco Corporate Drive Raleigh, NC 27617 (919)-297-3363 QuIC is a member of codeaurora.org

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. >> Virtio-net knows nothing above L2, so...

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. >> Virtio-net knows nothing above L2, so...

...ccept-ranges: bytes content-type: image/gif content-length: 3845 date: Wed, 22 May 2019 05:07:35 GMT expires: Wed, 22 May 2019 05:07:35 GMT cache-control: private, max-age=31536000 last-modified: Thu, 08 Dec 2016 01:00:57 GMT x-content-type-options: nosniff server: sffe x-xss-protection: 0 alt-svc: quic=":443"; ma=2592000; v="46,44,43,39" ``` Kind regards, Paul [1]: https://developer.r-project.org/

...file ? FWIW, the LDriw instruction is as show here. let isPredicable = 1 in def LDriw : LDInst<(outs IntRegs:$dst), (ins MEMri:$addr), "$dst = memw($addr)", [(set IntRegs:$dst, (i32 (load ADDRriS11_2:$addr)))]>; TIA, Pranav Qualcomm Innovation Center, (QuIC) is a member of the Code Aurora Forum.

> 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 and e.g. TCP is that TCP operates in a packet > > > > > loss environment. > > > > > So they are using timers for reliability, and receiver is > > > > > al...

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 and e.g. TCP is that TCP operates in a packet > > > > > loss environment. > > > > > So they are using timers for reliability, and receiver is > > > > > al...

...ffic? Or what is the fundamental reason that makes vsock does >> not go for virtio-net? > So virtio-vsock ensures reliability. It's done at the level of protocol instead of virtio transport or virtio device. > 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. Virtio-net knows nothing above L2, so they are totally transparent to...

...ffic? Or what is the fundamental reason that makes vsock does >> not go for virtio-net? > So virtio-vsock ensures reliability. It's done at the level of protocol instead of virtio transport or virtio device. > 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. Virtio-net knows nothing above L2, so they are totally transparent to...

...ile sources that contain these intrinsics, but with no success. In the process I found out that clang doesn't support NEON (as per http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html), but there has been at least some effort in adding it ( https://www.codeaurora.org/patches/quic/llvm/32040/clang-Initial-Neon-support.patch ). I also tried compiling LLVM 2.9 + llvm-gcc but that failed too many times and I gave up. After some discussions with colleagues (notably Alberto Magni, who added OpenCL support to clang some time ago http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-Nov...

...ndling code/tables compliant to > ARM's EH ABI? Probably not at first. It may require discussions with the specific front end folks (clang, llvm-gcc et al). Thanks for bringing it up tho., > > Thanks, > > -Dennis > > -- > Dennis Taul | Qualcomm Innovation Center,Inc. (QuIC) > 8041 Arco Corporate Drive > Raleigh, NC 27617 > (919)-297-3363 > QuIC is a member of codeaurora.org > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman...

...m> 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). The issues affect nginx compiled with the e...

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

...out" directive. *) Workaround: "gzip filter failed to use preallocated memory" alerts appeared in logs when using zlib-ng. *) Bugfix: nginx could not build libatomic library using the library sources if the --with-libatomic=DIR option was used. *) Bugfix: QUIC connection might not be established when using 0-RTT; the bug had appeared in 1.27.1. *) Bugfix: nginx now ignores QUIC version negotiation packets from clients. *) Bugfix: nginx could not be built on Solaris 10 and earlier with the ngx_http_v3_module. *) Bugfixe...