similar to: Discuss about the LLVM SW mitigation to Jump Conditional Code Erratum

I agree we shouldn’t try to guess what the user is trying to do. There shouldn’t be an unbounded set of heuristic rules; “documented” implies some sort of promise of stability in addition to the actual text in the manual. And we shouldn’t try to guess whether the user’s code cares about the length of a specific instruction. I think you’re creating a false dichotomy here, though. There’s some

FWIW I'm with Eli here if you need any more data points. -eric On Tue, Mar 24, 2020 at 8:21 PM Eli Friedman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Changing the length of a sequence of assembly instructions will break > someone’s code at some point. The length of a sequence of instructions is > known, in general, and people will write code to take advantage of

TLDR - We have a choice to make about assembler support, and a disagreement about how to move forward.  Community input needed. Background Intel has a hardware bug in Skylake and later whose mitigation requires padding of branches to avoid performance degradation. Background here:

I met with the Propeller team today (we work for the same company but it was my first time meeting two members on the team:) ). One thing I have been reassured: * There is no general disassembly work. General disassembly work would assuredly frighten off developers. (Inherently unreliable, memory usage heavy and difficult to deal with CFI, debug information, etc) Minimal amount of plumbing work

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2013-6885 / XSA-82 version 3 Guest triggerable AMD CPU erratum may cause host hang UPDATES IN VERSION 3 ==================== Early public release. This issue was predisclosed under embargo by the Xen Project Security team, on the 27th of November. We treated the issue

Hi I''ve installed Solaris snv111 in a QEMU virtual machine using qemu 0.10.2 with kqemu 1.4 enabled. The installation worked without problems but after rebooting from the virtual disk Solaris panics: qemu usage: /opt/qemu_0.10.x/bin/qemu-system-x86_64 -net user -net nic -usb -usbdevice tablet -L /usr/local/share/qemu_0.9.x -boot c -m 1024 -net nic,model=rtl8139 -net nic -net nic

Author: kucharsk Repository: /hg/zfs-crypto/gate Revision: b1f167e9bcec854103004aa601a56ab937e1223c Log message: 6288246 amd64 kernel needs to detect AMD Opteron erratum 131 Files: update: usr/src/uts/i86pc/Makefile.workarounds update: usr/src/uts/i86pc/os/cpuid.c update: usr/src/uts/i86pc/os/mp_startup.c update: usr/src/uts/intel/sys/controlregs.h

Author: kchow Repository: /hg/zfs-crypto/gate Revision: 1d1ea58da530f01d6bbadddd7bf5d0db64a0c96f Log message: 6295986 False AMD Erratum 123 warning message on stinger dual-core machines Files: update: usr/src/uts/i86pc/Makefile.workarounds update: usr/src/uts/i86pc/os/mp_startup.c

Hi, Ooops, mistake, please read host# tapdisk2 -n vhd:/storage/test.vhd instead of host# tapdisk2 -n vhc:/storage/test.vhd in my previous post. Kind regards, Sébastien _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Xiang, On Wed, Nov 11, 2020 at 1:59 AM Zhang, Xiang1 <xiang1.zhang at intel.com> wrote: > Jeremy wrote: > > ... The value %0 is live up to and including the ADD64ri but not past it, meaning LLVM today will drop the DBG_VALUE ... > > Just a little puzzle about the " drop the DBG_VALUE ", maybe I didn't get your key point, >

llvm-gcc is producing segmentation fault when running with -emit-llvm. Running cc1 in valgind produces the warning: ==12768== at 0x8D042C: llvm::llvm_ostream& llvm::llvm_ostream::operator<< <llvm::Module>(llvm::Module const&) (Streams.h:41) ==12768== by 0x8D0464: llvm::PrintModulePass::runOnModule(llvm::Module&) (PrintModulePass.h:41) ==12768== by 0xED6EB9:

Hi, My Server runs on Ubuntu Server 12.04 LTS 32 bits. I'm getting the following error messages when I run "make check" during the compilation of dovecot-2.2.13. <snip> ==2058== Conditional jump or move depends on uninitialised value(s) ==2058==??? at 0x4049DD8: inflateReset2 (in /lib/i386-linux-gnu/libz.so.1.2.3.4) ==2058==??? by 0x4049EC7: inflateInit2_ (in

On 11/30/2014 05:53 AM, AMM wrote: > __strspn_sse42 (in /lib64/libc-2.14.90.so) Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). If possible, upgrade your valgrind, libc etc. br, Teemu Huovila

On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > On 11/30/2014 05:53 AM, AMM wrote: >> __strspn_sse42 (in /lib64/libc-2.14.90.so) > Is it possible that you are encountering this issue? https://bugs.kde.org/show_bug.cgi?id=270925 > Either way, the error seems to stem from your libc implementation (if it is not the valgrind bug). > > If possible, upgrade your

On 12/01/2014 12:41 PM, AMM wrote: > > On Monday 01 December 2014 03:41 PM, Teemu Huovila wrote: > But Dovecot 2.2.10 (and earlier versions) were not throwing this error. This test was added in Dovecot version 2.2.14. It is also the only reference to strspn() in the whole project. > Can I can ignore it by NOT doing "make check"? I would say you can safely ignore it, but I

Hello, I am currently using Dovecot 2.2.10 on Fedora 16 - 64 bit system I had made v2.2.10 Fedora 16 rpm file using spec file from ATrpms. http://dl.atrpms.net/all/dovecot.spec It has been working well from 6 months or so. Today I tried to make v2.2.15 rpm using same spec file. But "make check" is giving following error: fatal_printf_format_fix

Hi, I'm using valgrind to check over some C/C++ code for an R library. I'm getting the report (see below), but can't track down the uninitialised value(s). I tried using --track-origins=yes in valgrind which gives: ==28258== Uninitialised value was created by a stack allocation ==28258== at 0xEE33D98: ??? (in /usr/lib64/R/lib/libRlapack.so) I presume the problem is an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Timo, Dovecot 2.2.6 compiled on Ubuntu 10.04 fails on "make check" with the following errors. "make install" is finishing just fine and Dovecot itself works flawlessly so far. - ----- 8< ----- http header invalid [0]: parse failure ............................... : ok: Expected ':' after header field name

I spent some time digging into a Valgrind report of uninitialized values in LLVM r287520 built using itself. (One of quite a few such reports that comes up during a "make check".) I could use another set of eyes on the issue if someone has time. This command gives me an error: valgrind -q ./bin/llc < /home/regehr/llvm/test/CodeGen/Hexagon/hwloop-dbg.ll -march=hexagon

On 01/19/2016 09:04 PM, Sean Silva via llvm-dev wrote: > > AFAIK, the cost of a well-predicted, not-taken branch is the same as a > nop on every x86 made in the last many years. > See http://www.agner.org/optimize/instruction_tables.pdf > <http://www.agner.org/optimize/instruction_tables.pdf> > Generally speaking a correctly-predicted not-taken branch is basically >