search for: l204

...ib/cmake/llvm/LLVMExports.cmake:1323 (message):   The imported target "yaml-bench" references the file      "/usr/lib/llvm-9/bin/yaml-bench"   but this file does not exist. Here's a minimal repro: https://travis-ci.org/weliveindetail/apt-llvm-9-dev-repro/builds/619590445#L204 Is anyone else seeing this too? Is there an obvious fix that I don't see? What's your workarounds? My current workaround is ridiculous, but works for me: https://github.com/weliveindetail/apt-llvm-9-dev-repro/commit/86497a3b#diff-3254677a7917c6c01f55212f86c57fbf Thanks Stefan -- https:...

...d target "yaml-bench" references the file >> >>       "/usr/lib/llvm-9/bin/yaml-bench" >> >>    but this file does not exist. >> >> Here's a minimal repro: >> https://travis-ci.org/weliveindetail/apt-llvm-9-dev-repro/builds/619590445#L204 >> >> >> Is anyone else seeing this too? Is there an obvious fix that I don't >> see? What's your workarounds? > yaml-bench is shipping in libclang-common-9-dev > > It should be indeed in llvm-9-dev instead. > > Could you please open a bug in > http...

https://bugs.freedesktop.org/show_bug.cgi?id=58806 Priority: medium Bug ID: 58806 Assignee: nouveau at lists.freedesktop.org Summary: failed to create kernel channel, -12 on G4 PPC QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: stefan at

> This seems like it was done for perf reason (mispredict). Conditional-to-cmov transformation should keep > from introducing additional observable side-effects, and it's clear that whatever did this did not account > for floating point exception. That’s a very reasonable statement, but I’m not sure it corresponds to the way we have typically approached this sort of problem. In

With the ATI bug I was hitting earlier fixed, only my btrfs partition continues to show high cpu usage for some operations. Rsync, git pull, git checkout and svn up are typicall operations which trigger the high cpu usage. As an example, this perf report is from using git checkout to change to a new branch; the change needed to checkout 208 files out of about 1600 total files. du(1) reports

...to u64 and double to u64. They are currently the only two operations that fail the RISC-V QEMU tests, which is essentially testing all of the compiler floating point intrinsics. https://github.com/michaeljclark/riscv-meta/blob/ea306062bfd2f60a229daf6b04826cdeb2dfbe9d/meta/opcode-pseudocode-c#L132-L204 These are the tests that I am using to exercise clang and gcc FENV_ACCESS along with the C code in the link above. riscv-qemu-tests is a user-mode port of the RISC-V ISA conformance test suite. - https://github.com/arsv/riscv-qemu-tests/tree/master/rv64f - https://github.com/arsv/riscv-qemu-tests...