[llvm-bugs] [Bug 34794] New: Mac OS .tar.xz release tarball hard to unpack on a Mac
https://bugs.llvm.org/show_bug.cgi?id=34794 Bug ID: 34794 Summary: Mac OS .tar.xz release tarball hard to unpack on a Mac Product: Packaging Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: binary tarballs Assignee: unassignedb...@nondot.org Reporter: richard-l...@metafoo.co.uk CC: llvm-bugs@lists.llvm.org Steps to reproduce: On macOS 10.12, download the release .tar.xz file and try to open it from Finder. Amazingly, the Mac "Archiver" tool runs and *compresses* the release to a .tar.xz.cpio file. As it happens, the Mac OS "tar" utility will automatically uncompress .xz compression when extracting (whether you ask it to or not)... but even this is an undocumented feature of the tar program. Could/should we ship a file format that the tools installed by default on the system are able to handle properly? .tar.gz files appear to be handled properly by default. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 33785] Wrong register in result asm when using inline asm with movups
https://bugs.llvm.org/show_bug.cgi?id=33785 Coby Tayree changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Coby Tayree --- fixed in rL314494 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34795] New: llvm-cov show: need to specify multiple -object's is unusable
https://bugs.llvm.org/show_bug.cgi?id=34795 Bug ID: 34795 Summary: llvm-cov show: need to specify multiple -object's is unusable Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: lebedev...@gmail.com CC: llvm-bugs@lists.llvm.org I was just experimenting with getting code coverage output from clang. When there is just one binary, then llvm-cov show works fine. But if the coverage data was merged from multiple binaries, to get the complete info about the full coverage, each of these binaries needs to be explicitly passed into llvm-cov show. This is rather unusable. It would be nice if there could be some native solution, much like what gcov/lcov already does, that would not require specifying every binary... For me, i should be able to solve it with some cmake magic though. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
