[llvm-bugs] [Bug 35987] Error when using linker scripts with ADDR and section names with '-'
https://bugs.llvm.org/show_bug.cgi?id=35987 Rafael Ávila de Espíndola changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Rafael Ávila de Espíndola --- Fixed in r322801. -- 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 35994] New: Duplicate vtables generated
https://bugs.llvm.org/show_bug.cgi?id=35994 Bug ID: 35994 Summary: Duplicate vtables generated Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: brucedaw...@chromium.org CC: llvm-bugs@lists.llvm.org Created attachment 19699 --> https://bugs.llvm.org/attachment.cgi?id=19699&action=edit A report of all vftable symbols that waste more than 31 bytes When running my ShowGlobals tool on the latest Chromium canary I noticed that many v-tables were showing up multiple times. The attached file is a report for chrome_child.dll.pdb. The first column is the number of excess copies of the `vftable' symbols - a value of 1 means there is 1 extra copy, or 2 total. The second column is the space wasted, in bytes. It is simply the size of the v-table times the first column. The third column is the symbol name. Possibly related to https://bugs.llvm.org/show_bug.cgi?id=31220? This duplication was not seen when building with VC++. The total waste is not huge but it seemed worth mentioning. It's not clear whether this is a problem with the compiler or linker. Objects that waste less than 32 bytes are not reported on (IIRC). -- 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 35993] New: Write a TargetMachine creation API to replace EngineBuilder
https://bugs.llvm.org/show_bug.cgi?id=35993 Bug ID: 35993 Summary: Write a TargetMachine creation API to replace EngineBuilder Product: libraries Version: trunk Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: OrcJIT Assignee: unassignedb...@nondot.org Reporter: lha...@gmail.com CC: llvm-bugs@lists.llvm.org ORC layers / components often need access to an llvm::TargetMachine (e.g. the SimpleComplier class requires one). To date we've been relying on EngineBuilder::selectTarget from ExecutionEngine, but this has a couple of drawbacks: the interface and implementation are designed around ExecutionEngine's assumptions (i.e. you're building an ExecutionEngine subclass, that subclass might be an interpreter, etc.). The code is also older and doesn't do any CPU feature detection. We should design a new interface for building TargetMachines for LLVM JITs. It should be clean, able to support CPU feature detection, and ideally efficiently queryable from a remote machine (for remote execution). -- 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 35989] dump_ast_matchers.py completely ignores short matchers
https://bugs.llvm.org/show_bug.cgi?id=35989 Benjamin Kramer changed: What|Removed |Added CC||benny@gmail.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Benjamin Kramer --- r322783 fixes the one-line thing. I don't think we want to support newlines between decls and comments. -- 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 34076] clang crashes on conversion from __float128 to long double
https://bugs.llvm.org/show_bug.cgi?id=34076 Benjamin Kramer changed: What|Removed |Added CC||benny@gmail.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Benjamin Kramer --- Fixed in r322772. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35814, which changed state. Bug 35814 Summary: After r316416, Assertion failed: ((size_t)StackDisp < Context.MovVector.size() && "Function call has more parameters than the stack is adjusted for."), function collectCallInfo, file lib/Target/X86/X86CallFrameOptimization.c https://bugs.llvm.org/show_bug.cgi?id=35814 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- 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 35814] After r316416, Assertion failed: ((size_t)StackDisp < Context.MovVector.size() && "Function call has more parameters than the stack is adjusted for."), function collectCallInfo
https://bugs.llvm.org/show_bug.cgi?id=35814 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Reid Kleckner --- As discussed on the patch, I think this is actually PR31362, which is that ms_abi just doesn't work for structs larger than 8 bytes. It uses the Linux calling convention logic, which is wrong. We could keep open a separate issue for making byval not generate crashing code on win64, but I don't think it's worth it. *** This bug has been marked as a duplicate of bug 31362 *** -- 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 29143] va_arg in ms_abi variadic functions should expect large structs to be passed by reference
https://bugs.llvm.org/show_bug.cgi?id=29143 Reid Kleckner changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Reid Kleckner --- *** This bug has been marked as a duplicate of bug 31362 *** -- 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 33834] [ms_abi] Big structures arguments are not passed correctly (x64)
https://bugs.llvm.org/show_bug.cgi?id=33834 Reid Kleckner changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Reid Kleckner --- *** This bug has been marked as a duplicate of bug 31362 *** -- 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 35992] New: ld cannot find crtbegin.o Amazon AMI, ignores -L/path/.../
https://bugs.llvm.org/show_bug.cgi?id=35992
Bug ID: 35992
Summary: ld cannot find crtbegin.o Amazon AMI, ignores
-L/path/.../
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: oma...@seas.upenn.edu
CC: llvm-bugs@lists.llvm.org
I compiled from source LLVM 6.0 on an Amazon Linux AMI 2017.09.1.20171120
x86_64
When attempting to compile a trivial program:
clang test.c -o test
ld fails with the following output:
/usr/bin/ld: cannot find crtbegin.o: No such file or directory
clang-6.0: error: linker command failed with exit code 1 (use -v to see
invocation)
Doing a find for crtbegin.o yields:
$ sudo find / -name "crtbegin.o" | grep -v "llvm"
/usr/lib/gcc/x86_64-amazon-linux/7/crtbegin.o
/usr/lib/gcc/x86_64-amazon-linux/4.8.5/32/crtbegin.o
/usr/lib/gcc/x86_64-amazon-linux/4.8.5/crtbegin.o
Adding -L/usr/lib/gcc/x86_64-amazon-linux/7/ or
-L/usr/lib/gcc/x86_64-amazon-linux/4.8.5/ did not help.
Running in verbose mode I can see the exact place it fails:
"/usr/bin/ld" --eh-frame-hdr -m elf_x86_64 -dynamic-linker
/lib64/ld-linux-x86-64.so.2 -o a.out /usr/lib/../lib64/crt1.o
/usr/lib/../lib64/crti.o crtbegin.o -L/usr/lib/gcc/x86_64-amazon-linux/4.8.5/
-L/opt/nvidia/cuda/lib64/ -L/lib/../lib64 -L/usr/lib/../lib64
-L/home/ec2-user/Programs/llvm6-build/bin/../lib -L/lib -L/usr/lib
/tmp/gaussian-5f5074.o -lcudart_static -ldl -lrt -lstdc++ -lm -lgcc_s -lgcc
-lpthread -lc -lgcc_s -lgcc crtend.o /usr/lib/../lib64/crtn.o
/usr/bin/ld: cannot find crtbegin.o: No such file or directory
It seems to ignore the two directories I passed in.
To fix it, I straced the paths that ld was checking:
> strace -f clang test.c -o test 2>&1 | grep "crtbegin.o"
access("/home/ec2-user/Programs/llvm6-build/lib/clang/6.0.0/crtbegin.o", F_OK)
= -1 ENOENT (No such file or directory)
access("/home/ec2-user/Programs/llvm6-build/lib/clang/6.0.0/lib/linux/crtbegin.o",
F_OK) = -1 ENOENT (No such file or directory)
access("/lib/../lib64/crtbegin.o", F_OK) = -1 ENOENT (No such file or
directory)
access("/usr/lib/../lib64/crtbegin.o", F_OK) = -1 ENOENT (No such file or
directory)
access("/home/ec2-user/Programs/llvm6-build/bin/../lib/crtbegin.o", F_OK) = -1
ENOENT (No such file or directory)
access("/lib/crtbegin.o", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/crtbegin.o", F_OK) = -1 ENOENT (No such file or directory)
[pid 6469] execve("/usr/bin/ld", ["/usr/bin/ld", "--eh-frame-hdr", "-m",
"elf_x86_64", "-dynamic-linker", "/lib64/ld-linux-x86-64.so.2", "-o", "test",
"/usr/lib/../lib64/crt1.o", "/usr/lib/../lib64/crti.o", "crtbegin.o",
"-L/lib/../lib64", "-L/usr/lib/../lib64",
"-L/home/ec2-user/Programs/llvm6-"..., "-L/lib", "-L/usr/lib", ...], [/* 14
vars */]
[pid 6469] open("crtbegin.o", O_RDONLY) = -1 ENOENT (No such file or
directory)
[pid 6469] write(2, "crtbegin.o", 10crtbegin.o) = 10
I ended up creating symlinks to the folders where ld was looking:
> sudo ln -s /usr/lib/gcc/x86_64-amazon-linux/7/crtbegin.o /lib/../lib64/
> sudo ln -s /usr/lib/gcc/x86_64-amazon-linux/7/crtend.o /lib/../lib64/
This fixed all my issues.
--
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 35991] New: [lldb] Please backport LLDB test regression fixes to 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35991 Bug ID: 35991 Summary: [lldb] Please backport LLDB test regression fixes to 6.0 branch Product: lldb Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org Blocks: 35804 Please backport the two following commits that are necessary to fix test runner regressions introduced in 6.0: r322081 [test] Fix tests to use more portable LLVM_ENABLE_ZLIB r321932 [test] Use full PATH lookup for tools Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.0.0 Release Blockers -- 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 35926] [ARM] TableGen doesn't select VFNMSD
https://bugs.llvm.org/show_bug.cgi?id=35926 daniel_l_sand...@apple.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from daniel_l_sand...@apple.com --- Fixed in r322754 -- 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 35990] New: std::experimental::filesystem::file_time_type::min() exceeds values supported by the underlying file system
https://bugs.llvm.org/show_bug.cgi?id=35990 Bug ID: 35990 Summary: std::experimental::filesystem::file_time_type::min() exceeds values supported by the underlying file system Product: libc++ Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: vsap...@apple.com CC: e...@efcs.ca, llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Created attachment 19698 --> https://bugs.llvm.org/attachment.cgi?id=19698&action=edit Code to test with low-level API. std::experimental::filesystem::file_time_type::min() exceeds values supported by the underlying file system. When you set file modification time with filesystem::last_write_time(path, time) with min value and read it back with filesystem::last_write_time(path), received value can be significantly different from the supplied one. Steps to reproduce: 1. Call auto min_time = std::experimental::filesystem::file_time_type::min(); std::experimental::filesystem::last_write_time(path, min_time); 2. Call auto current_time = std::experimental::filesystem::last_write_time(path); 3. Reboot machine you are running the test on. 4. Call auto current_time2 = std::experimental::filesystem::last_write_time(path); Expected result: min_time, current_time, current_time2 should be equal, at least to the second. Actual result: Results depend on the underlying file system. On macOS with APFS min_time != current_time, current_time == current_time2. Inequality is detected by the test std/experimental/filesystem/fs.op.funcs/fs.op.last_write_time/last_write_time.pass.cpp On Ubuntu 16.04.3 with ext3 min_time == current_time, current_time != current_time2. Details: For writing and reading file modification timestamp we are using utimensat and stat, respectively. In my testing filesystem::file_time_type::min() was -2^63 microseconds which can be expressed with `struct timespec` which has 64-bit tv_sec and 64-bit tv_nsec. But file systems I tested don't use 128 bits to store timestamps on the disk. One common approach seems to be using 128-bit value while inode metadata is still in memory. That allows the test last_write_time.pass.cpp to pass on ext3 and probably ext4. But according to POSIX.1-2008 http://pubs.opengroup.org/onlinepubs/9699919799/ that is not conformant > Upon assignment, file timestamps are immediately converted to the resolution > of the file system by truncation (i.e., the recorded time can be older than > the actual time). For example, if the file system resolution is 1 > microsecond, then a conforming stat() must always return an st_mtim.tv_nsec > that is a multiple of 1000. Some older implementations returned > higher-resolution timestamps while the inode information was cached, and then > spontaneously truncated the tv_nsec fields when they were stored to and > retrieved from disk, but this behavior does not conform. > - Section 11. Headers, Regardless of the POSIX standard, I think the developers expect that values in file_time_type::min()/max() range are safe to use and won't change on their own. I have attached `testing.c` to test utimensat and stat directly and the results are On APFS: Will update file mtime to tv_sec = -9223372036854, tv_nsec = 0 File mtime now is tv_sec = -9223372036, tv_nsec = -854775808 On ext3: Will update file mtime to tv_sec = -9223372036854, tv_nsec = 0 File mtime now is tv_sec = -9223372036854, tv_nsec = 0 after rebooting File mtime now is tv_sec = 2217714954, tv_nsec = 0 -- 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 35989] New: dump_ast_matchers.py completely ignores short matchers
https://bugs.llvm.org/show_bug.cgi?id=35989
Bug ID: 35989
Summary: dump_ast_matchers.py completely ignores short matchers
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Documentation
Assignee: unassignedclangb...@nondot.org
Reporter: lebedev...@gmail.com
CC: llvm-bugs@lists.llvm.org
E.g. it is fine with
AST_MATCHER(FunctionDecl, isNoReturn) {
return Node.isNoReturn();
}
but not with
AST_MATCHER(FunctionDecl, isNoReturn) { return Node.isNoReturn(); }
--
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 35953] Clang crashing when it encounters '#line 1' in c++-header
https://bugs.llvm.org/show_bug.cgi?id=35953 Reid Kleckner changed: What|Removed |Added Resolution|--- |DUPLICATE CC||r...@google.com Status|NEW |RESOLVED --- Comment #4 from Reid Kleckner --- *** This bug has been marked as a duplicate of bug 31944 *** -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35876, which changed state. Bug 35876 Summary: Merge r322003 into 6.0 release https://bugs.llvm.org/show_bug.cgi?id=35876 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35876] Merge r322003 into 6.0 release
https://bugs.llvm.org/show_bug.cgi?id=35876 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Hans Wennborg --- Merged in r322693. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35806, which changed state. Bug 35806 Summary: Merge r321751 into the 6.0 branch : StructurizeCFG: Fix broken backedge detection https://bugs.llvm.org/show_bug.cgi?id=35806 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35806] Merge r321751 into the 6.0 branch : StructurizeCFG: Fix broken backedge detection
https://bugs.llvm.org/show_bug.cgi?id=35806 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35954, which changed state. Bug 35954 Summary: Merge clang r322390 into 6.0 branch: [Lex] Avoid out-of-bounds dereference in LexAngledStringLiteral. https://bugs.llvm.org/show_bug.cgi?id=35954 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35954] Merge clang r322390 into 6.0 branch: [Lex] Avoid out-of-bounds dereference in LexAngledStringLiteral.
https://bugs.llvm.org/show_bug.cgi?id=35954 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||h...@chromium.org --- Comment #1 from Hans Wennborg --- It was merged in r322649. -- 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 35916] merge r322313 to 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35916 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #3 from Hans Wennborg --- Merged in r322684. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35916, which changed state. Bug 35916 Summary: merge r322313 to 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35916 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35915, which changed state. Bug 35915 Summary: Merge clang r322246 into 6.0 branch: [X86] Fix vpshrd builtins to require an ICE for their constant argument to match vpshld. https://bugs.llvm.org/show_bug.cgi?id=35915 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35915] Merge clang r322246 into 6.0 branch: [X86] Fix vpshrd builtins to require an ICE for their constant argument to match vpshld.
https://bugs.llvm.org/show_bug.cgi?id=35915 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #2 from Hans Wennborg --- Merged in r322682. -- 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 35893] Merge r322223 into 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35893 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||h...@chromium.org --- Comment #1 from Hans Wennborg --- Merged in r322681. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35893, which changed state. Bug 35893 Summary: Merge r33 into 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35893 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35865] [SLP] Regression (r310260): Not a vector MVT! UNREACHABLE executed
https://bugs.llvm.org/show_bug.cgi?id=35865 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED CC||h...@chromium.org Status|REOPENED|RESOLVED --- Comment #3 from Hans Wennborg --- Merged in r322680. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35865, which changed state. Bug 35865 Summary: [SLP] Regression (r310260): Not a vector MVT! UNREACHABLE executed https://bugs.llvm.org/show_bug.cgi?id=35865 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35820, which changed state. Bug 35820 Summary: LLVM 6 fails to compile pocl's shuffle test https://bugs.llvm.org/show_bug.cgi?id=35820 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35820] LLVM 6 fails to compile pocl's shuffle test
https://bugs.llvm.org/show_bug.cgi?id=35820 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Hans Wennborg --- Merged in r322679. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35817, which changed state. Bug 35817 Summary: Merge r321779 into the 6.0 branch: PR35045: Convert injected-class-name to its corresponding simple-template-id https://bugs.llvm.org/show_bug.cgi?id=35817 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35816, which changed state. Bug 35816 Summary: Merge r321777 into the 6.0 branch: PR35028: Retain duplicate alignas attributes in template instantiation. https://bugs.llvm.org/show_bug.cgi?id=35816 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35816] Merge r321777 into the 6.0 branch: PR35028: Retain duplicate alignas attributes in template instantiation.
https://bugs.llvm.org/show_bug.cgi?id=35816 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- Merged in r322676. -- 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 35988] New: [AMDGPU][MC] Image atomic operations failed to disassemble
https://bugs.llvm.org/show_bug.cgi?id=35988 Bug ID: 35988 Summary: [AMDGPU][MC] Image atomic operations failed to disassemble Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org Decoder namespace is not specified for image atomics -- 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 35777] Invalid InsertValueInst operands!
https://bugs.llvm.org/show_bug.cgi?id=35777 Hans Wennborg changed: What|Removed |Added Status|REOPENED|RESOLVED CC||h...@chromium.org Resolution|--- |FIXED --- Comment #8 from Hans Wennborg --- Merged to 6.0 in r322675. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35777, which changed state. Bug 35777 Summary: Invalid InsertValueInst operands! https://bugs.llvm.org/show_bug.cgi?id=35777 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35773, which changed state. Bug 35773 Summary: clang crashes at -O2 and above: : Assertion `!hasVectorValue(Key, Part) && "Vector value already set for part"' failed. https://bugs.llvm.org/show_bug.cgi?id=35773 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35773] clang crashes at -O2 and above: : Assertion `!hasVectorValue(Key, Part) && "Vector value already set for part"' failed.
https://bugs.llvm.org/show_bug.cgi?id=35773 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||h...@chromium.org --- Comment #7 from Hans Wennborg --- Merged in r322673. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35763, which changed state. Bug 35763 Summary: -O0 bug: long bitfields triggering incorrect code https://bugs.llvm.org/show_bug.cgi?id=35763 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- 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 35763] -O0 bug: long bitfields triggering incorrect code
https://bugs.llvm.org/show_bug.cgi?id=35763 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Hans Wennborg --- Merged in r322671. -- 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 35761] Clang -O0: "cast() argument of incompatible type"
https://bugs.llvm.org/show_bug.cgi?id=35761 Hans Wennborg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #5 from Hans Wennborg --- Merged to 6.0 in r322670. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35761, which changed state. Bug 35761 Summary: Clang -O0: "cast() argument of incompatible type" https://bugs.llvm.org/show_bug.cgi?id=35761 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 35987] New: Error when using linker scripts with ADDR and section names with '-'
https://bugs.llvm.org/show_bug.cgi?id=35987
Bug ID: 35987
Summary: Error when using linker scripts with ADDR and section
names with '-'
Product: lld
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: roy...@freebsd.org
CC: llvm-bugs@lists.llvm.org
Hello,
I have the following sample linker script, it's basically an extract of a much
bigger linker file
---
SECTIONS
{
.note.gnu.build-id : AT(ADDR(.note.gnu.build-id)) {
*(.note.gnu.build-id)
} :text
}
---
Which I try to use with lld, giving the following error:
$ ld --build-id=sha1 -T test.lds
ld: error: test.lds:3: ) expected, but got -
ld: error: test.lds:3: .note.gnu.build-id : AT(ADDR(.note.gnu.build-id)) {
ld: error: test.lds:3: ^
ld: error: target emulation unknown: -m or at least one .o file required
Ignoring the error about the lack of input files or emulation, it seems like
ADDR somehow checks that the parameter of ADDR is not an expression, but fails
to realise that sections can have '-' in their names.
The output with GNU ld is:
$ ld --build-id=sha1 -T test.lds
/usr/local/bin/ld: no input files
And I can confirm using ADDR(.note.gnu.build-id) with GNU ld works fine.
Thanks, Roger.
--
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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35628, which changed state. Bug 35628 Summary: [SLP] "Replacing out-of-tree value with undef" in SLPVectorizer.cpp https://bugs.llvm.org/show_bug.cgi?id=35628 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- 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 35628] [SLP] "Replacing out-of-tree value with undef" in SLPVectorizer.cpp
https://bugs.llvm.org/show_bug.cgi?id=35628 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Hans Wennborg --- (In reply to Simon Pilgrim from comment #4) > Reopening until its merged into the 6.00 release branch Merged in r322669. -- 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] Issue 5455 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() == getType() && "replaceAllUses of value with new value of differ
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-17 Type: Bug New issue 5455 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() == getType() && "replaceAllUses of value with new value of differ https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5455 Detailed report: https://oss-fuzz.com/testcase?key=5667930743242752 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: New->getType() == getType() && "replaceAllUses of value with new value of differ llvm::Value::doRAUW llvm::BitcodeReaderValueList::assignValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5667930743242752 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35534] Wasm backend duplicate function pruning
https://bugs.llvm.org/show_bug.cgi?id=35534 Nicholas Wilson changed: What|Removed |Added Status|NEW |RESOLVED CC||n...@realvnc.com Resolution|--- |FIXED --- Comment #1 from Nicholas Wilson --- Duplicate functions are now pruned in LLD as of r322415. In D41390 (https://reviews.llvm.org/D41390), there was a discussion of whether duplicate weak (but not COMDAT) symbols should be pruned by LLD. Since that behaviour is handled by GC for LLD-ELF, we decided not to do the weak symbol pruning until LLD-Wasm gets GC support. -- 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 35533] Wasm backend COMDAT support
https://bugs.llvm.org/show_bug.cgi?id=35533 Nicholas Wilson changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #22 from Nicholas Wilson --- Working COMDAT support was merged in r322415 (https://reviews.llvm.org/D40845) for LLD, https://reviews.llvm.org/D40844 for LLVM. The model uses "COMDAT groupings" of symbols that are linked/discarded together. We don't have GC yet, so the symbols are selected together automatically, and the "discard these syms together" behaviour is explicit. The implementation matches the ELF linker's implementation of COMDAT groups - but that could be revised in future. -- 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 35544] Wasm: add new weak global symbol "__stack_top"
https://bugs.llvm.org/show_bug.cgi?id=35544 Nicholas Wilson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Nicholas Wilson --- This was fixed in r322609 (D42030). The symbol is called "__heap_base" (not "__stack_top" or "__heap_bottom" as described above). -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35986, which changed state. Bug 35986 Summary: Merge libc++ r321963 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35986 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35986] Merge libc++ r321963 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35986 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- Merged in r322659. Marshall, please shout if you have any objections. -- 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] Issue 3817 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: result <= UINT32_MAX
Updates: Labels: Deadline-Approaching Comment #8 on issue 3817 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3817#c8 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3822 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in llvm_llvm-dwarfdump-fuzzer
Updates: Labels: Deadline-Approaching Comment #7 on issue 3822 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in llvm_llvm-dwarfdump-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3822#c7 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3815 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Crash in llvm::object::WasmObjectFile::parseDataSection
Updates: Labels: Deadline-Approaching Comment #8 on issue 3815 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Crash in llvm::object::WasmObjectFile::parseDataSection https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3815#c8 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3814 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in readInitExpr
Updates: Labels: Deadline-Approaching Comment #7 on issue 3814 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in readInitExpr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3814#c7 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35749] After r315899, .byte directives after x86 prefixes cause errors
https://bugs.llvm.org/show_bug.cgi?id=35749 Hans Wennborg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Hans Wennborg --- D42102 has been committed and merged. Please re-open if anything else needs to be done here. -- 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 10988] x86 MC encoder and disassembler bugs umbrella
https://bugs.llvm.org/show_bug.cgi?id=10988 Bug 10988 depends on bug 35749, which changed state. Bug 35749 Summary: After r315899, .byte directives after x86 prefixes cause errors https://bugs.llvm.org/show_bug.cgi?id=35749 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 35986] New: Merge libc++ r321963 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35986 Bug ID: 35986 Summary: Merge libc++ r321963 into the 6.0 branch Product: libc++ Version: 6.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: dimi...@andric.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Please merge https://reviews.llvm.org/rL321963 into the 6.0 branch for libc++. This fixes compiling with gcc in pre-C++11 mode. -- 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 35976] Merge r321459 and r322623 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35976 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Hans Wennborg --- r321459 landed before the branch. r322623 I've merged in r322654. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35976, which changed state. Bug 35976 Summary: Merge r321459 and r322623 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35976 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35031] clang-cl /FA should probably default to intel syntax
https://bugs.llvm.org/show_bug.cgi?id=35031 Nico Weber changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nico Weber --- http://llvm.org/viewvc/llvm-project?view=revision&revision=322652 -- 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 35943] [lld] Merge 321657 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35943 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Hans Wennborg --- r321657 is slightly before the branch, so it's already in 6.0. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35943, which changed state. Bug 35943 Summary: [lld] Merge 321657 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35943 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35942, which changed state. Bug 35942 Summary: Merge r322282 into the 6.0 branch: Fix for libomp static build https://bugs.llvm.org/show_bug.cgi?id=35942 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- 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 35942] Merge r322282 into the 6.0 branch: Fix for libomp static build
https://bugs.llvm.org/show_bug.cgi?id=35942 Hans Wennborg changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- IIUC, the fix is for a problem introduced in r322202, which landed after the branch. Please re-open if something still needs to be done. -- 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 35977] Vector shift misoptimized with AVX512
https://bugs.llvm.org/show_bug.cgi?id=35977 Benjamin Kramer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Benjamin Kramer --- It was r321085. Fixed in r322644. -- 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 35904] [lld] Merge r321986, r322041 and r322264 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35904 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Hans Wennborg --- r321986 was merged as r322565. I've merged r322041 in r322647, and r322264 in r322648. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35904, which changed state. Bug 35904 Summary: [lld] Merge r321986, r322041 and r322264 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35904 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35868, which changed state. Bug 35868 Summary: Merge r321986 and r322041 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35868 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- 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 35868] Merge r321986 and r322041 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35868 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED CC||h...@chromium.org Resolution|--- |DUPLICATE --- Comment #4 from Hans Wennborg --- *** This bug has been marked as a duplicate of bug 35904 *** -- 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 35799] clang crashes on valid code at -O2 and -O3 on x86_64-linux-gnu in 32-bit mode: Assertion `ScaledReg == nullptr' failed
https://bugs.llvm.org/show_bug.cgi?id=35799 Hans Wennborg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Hans Wennborg --- (In reply to Simon Pilgrim from comment #10) > (In reply to Serguei Katkov from comment #9) > > Does it make sense to re-assign it to someone who is responsible for merge > > to release branch (Hans?)? > > Won't do any harm, but Hans (et al) can already see it as an open dependency > on Bug #35804. Merged in r322645. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35799, which changed state. Bug 35799 Summary: clang crashes on valid code at -O2 and -O3 on x86_64-linux-gnu in 32-bit mode: Assertion `ScaledReg == nullptr' failed https://bugs.llvm.org/show_bug.cgi?id=35799 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35894, which changed state. Bug 35894 Summary: merge r322236 to clang 6 branch https://bugs.llvm.org/show_bug.cgi?id=35894 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35883, which changed state. Bug 35883 Summary: Merge r322160 into the 6.0 branch: [OMPT] Fix cast and printf of wait_id in lock test https://bugs.llvm.org/show_bug.cgi?id=35883 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 35883] Merge r322160 into the 6.0 branch: [OMPT] Fix cast and printf of wait_id in lock test
https://bugs.llvm.org/show_bug.cgi?id=35883 Hans Wennborg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Hans Wennborg --- Merged in r322640. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35872, which changed state. Bug 35872 Summary: Merge r322068 into the 6.0 branch: Fix type mismatch in omp_control_tool() implementation that makes it run incorrectly on 32-bit machines. https://bugs.llvm.org/show_bug.cgi?id=35872 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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 35872] Merge r322068 into the 6.0 branch: Fix type mismatch in omp_control_tool() implementation that makes it run incorrectly on 32-bit machines.
https://bugs.llvm.org/show_bug.cgi?id=35872 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Hans Wennborg --- Merged in r322639. -- 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35981, which changed state. Bug 35981 Summary: Merge r322350 and related commits into 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35981 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 35981] Merge r322350 and related commits into 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35981 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- Merged in r322632. -- 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 35985] New: [AArch64] AArch64DAGToDAGISel::SelectPostLoadLane hits invalid cast
https://bugs.llvm.org/show_bug.cgi?id=35985 Bug ID: 35985 Summary: [AArch64] AArch64DAGToDAGISel::SelectPostLoadLane hits invalid cast Product: new-bugs Version: 5.0 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: serge.guel...@telecom-bretagne.eu CC: llvm-bugs@lists.llvm.org Created attachment 19695 --> https://bugs.llvm.org/attachment.cgi?id=19695&action=edit input, reduced minimal test case The reduced .ll file, when compiled with > ./bin/clang -cc1 -triple aarch64--linux-android -emit-obj buggy-4.ll hits the following traceback: #0 0x7fbdcc61d43f llvm::sys::PrintStackTrace(llvm::raw_ostream&) .../_build/../lib/Support/Unix/Signals.inc:398:13 #1 0x7fbdcc61d746 bool __gnu_cxx::operator!=*, std::vector, std::allocator > > >(__gnu_cxx::__normal_iterator*, std::vector, std::allocator > > > const&, __gnu_cxx::__normal_iterator*, std::vector, std::allocator > > > const&) /usr/bin/../lib/gcc/x86_64-linux-gnu/7.2.0/../../../../include/c++/7.2.0/bits/stl_iterator.h:883:27 #2 0x7fbdcc61d746 llvm::sys::RunSignalHandlers() .../_build/../lib/Support/Signals.cpp:49:0 #3 0x7fbdcc61d746 SignalHandler(int) .../_build/../lib/Support/Unix/Signals.inc:242:0 #4 0x7fbdcbca8160 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12160) #5 0x7fbdc987b6a0 gsignal (/lib/x86_64-linux-gnu/libc.so.6+0x346a0) #6 0x7fbdc987ccf7 abort (/lib/x86_64-linux-gnu/libc.so.6+0x35cf7) #7 0x7fbdc9873fca (/lib/x86_64-linux-gnu/libc.so.6+0x2cfca) #8 0x7fbdc9874042 (/lib/x86_64-linux-gnu/libc.so.6+0x2d042) #9 0x7fbddb19f439 llvm::APInt::getZExtValue() const .../_build/../include/llvm/ADT/APInt.h:1545:5 #10 0x7fbddb19f439 llvm::ConstantInt::getZExtValue() const .../_build/../include/llvm/IR/Constants.h:150:0 #11 0x7fbddb19f439 llvm::ConstantSDNode::getZExtValue() const .../_build/../include/llvm/CodeGen/SelectionDAGNodes.h:1437:0 #12 0x7fbddb19f439 (anonymous namespace)::AArch64DAGToDAGISel::SelectPostLoadLane(llvm::SDNode*, unsigned int, unsigned int) .../_build/../lib/Target/AArch64/AArch64ISelDAGToDAG.cpp:1382:0 #13 0x7fbdc903c49a llvm::SelectionDAGISel::DoInstructionSelection() .../_build/../lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:944:28 #14 0x7fbdc903b99d llvm::TimeRegion::~TimeRegion() .../_build/../include/llvm/Support/Timer.h:152:9 #15 0x7fbdc903b99d llvm::SelectionDAGISel::CodeGenAndEmitDAG() .../_build/../lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:848:0 #16 0x7fbdc90391cf llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) .../_build/../lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:1609:11 #17 0x7fbdc90361d6 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) .../_build/../lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:467:7 #18 0x7fbdce6e1604 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) .../_build/../lib/CodeGen/MachineFunctionPass.cpp:62:13 #19 0x7fbdce14902f llvm::FPPassManager::runOnFunction(llvm::Function&) .../_build/../lib/IR/LegacyPassManager.cpp:1514:27 #20 0x7fbdce149283 llvm::FPPassManager::runOnModule(llvm::Module&) .../_build/../lib/IR/LegacyPassManager.cpp:1535:13 #21 0x7fbdce149779 (anonymous namespace)::MPPassManager::runOnModule(llvm::Module&) .../_build/../lib/IR/LegacyPassManager.cpp:1591:27 #22 0x7fbdce149779 llvm::legacy::PassManagerImpl::run(llvm::Module&) .../_build/../lib/IR/LegacyPassManager.cpp:1694:0 -- 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 35984] New: Failure to capture variable from structured binding
https://bugs.llvm.org/show_bug.cgi?id=35984
Bug ID: 35984
Summary: Failure to capture variable from structured binding
Product: new-bugs
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: svalor...@gmail.com
CC: llvm-bugs@lists.llvm.org
```
#include
std::tuple a() { return std::make_tuple(0, 0.4); }
int main() {
auto [x, y] = a();
const auto q = [x](){ return true; };
return 0;
}
```
This fails to compile with
7 : :7:21: error: 'x' in capture list does not name a variable
const auto q = [x](){ return true; };
This breaks on my machine with clang++ 4.0. I have also tested this on clang++
5.0 on godbolt.org.
--
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 35983] New: piglit builtin-float-cos-1.0 crashes with llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:916: llvm::SelectionDAG::~SelectionDAG(): Assertion `!UpdateListeners && "Dangling
https://bugs.llvm.org/show_bug.cgi?id=35983 Bug ID: 35983 Summary: piglit builtin-float-cos-1.0 crashes with llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:916: llvm::SelectionDAG::~SelectionDAG(): Assertion `!UpdateListeners && "Dangling registered DAGUpdateListeners"' failed. Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Keywords: regression Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: pavel.ondra...@email.cz CC: jan.ves...@rutgers.edu, llvm-bugs@lists.llvm.org, matthew.arsena...@amd.com Created attachment 19693 --> https://bugs.llvm.org/attachment.cgi?id=19693&action=edit compressed full backtrace Three piglit tests: builtin-float-cos-1.0.generated builtin-float-sin-1.0.generated builtin-float-tan-1.0.generated crash with llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:917: llvm::SelectionDAG::~SelectionDAG(): Assertion `!UpdateListeners && "Dangling registered DAGUpdateListeners"' failed. This is a regressing. I have run a regression tests, however due to unrelated build failure I ended with quite lot of skips. By manually reverting the related looking ones on top of first bad building revision (a83daa1) I found that two commits must be reverted to get the test working again. The first one is the likely culprit, while the second one is probably only a build fix. commit f68b9beeb97bd44cc651d519c45e8ad32067825d Author: Jan Vesely Date: Mon Dec 4 23:07:28 2017 + AMDGPU/EG: Add a new FeatureFMA and use it to selectively enable FMA instruction Only used by pre-GCN targets v2: fix predicate setting for FMA_Common commit a7574026a1ac25d5955e8e29c4b5ec59ac0f6576 Author: Matt Arsenault Date: Tue Dec 5 03:15:44 2017 + AMDGPU: Fix missing subtarget feature initializer The testing was done with latest mesa, libclc and CAICOS GPU. Bug 35910 may be related. It has the same symptoms, however as the app mentioned there was not working even before the aforementioned commits, it is unclear if this is the same root cause. -- 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 35982] New: [MMX] POSTRAScheduler rearrange emms and mmx instruction
https://bugs.llvm.org/show_bug.cgi?id=35982
Bug ID: 35982
Summary: [MMX] POSTRAScheduler rearrange emms and mmx
instruction
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: ilia.tara...@intel.com
CC: llvm-bugs@lists.llvm.org
POSTRAScheduler rearrange emms and mmx instruction, so we receive wrong result:
= main.c ==
#include
#include
float sum(__m64);
int main()
{
float result;
__m64 x = (_mm_set_pi32(5, 3));
result = sum(x);
printf("5 + 3 = %f\n", result);
_mm_empty();
return 0;
}
===
= nice.c ==
#include
float sum(__m64 x)
{
double t;
int x1, x2;
x1 = _mm_cvtsi64_si32(x);
x2 = _mm_cvtsi64_si32(_mm_unpackhi_pi32(x, x));
_mm_empty();
t = (float)x1 + (float)x2;
return t;
}
===
>>> clang -v
clang version 7.0.0 (trunk 322555)
Target: x86_64-unknown-linux-gnu
Thread model: posix
...
>>> clang -m32 -O0 -o nice.exe main.c nice.c
>>> ./nice.exe
5 + 3 = 8.00
>>> clang -m32 -O2 -o nice.exe main.c nice.c
>>> ./nice.exe
5 + 3 = -nan
>>> clang -m32 -O2 -o nice.exe main.c nice.c -mllvm -opt-bisect-limit=194 &&
>>> ./nice.exe
...
BISECT: running pass (193) Tail Duplication on function (sum)
BISECT: running pass (194) Machine Copy Propagation Pass on function (sum)
BISECT: NOT running pass (195) Post RA top-down list latency scheduler on
function (sum)
BISECT: NOT running pass (196) Branch Probability Basic Block Placement on
function (sum)
...
5 + 3 = 8
>>> clang -m32 -O2 -o nice.exe main.c nice.c -mllvm -opt-bisect-limit=195 &&
>>> ./nice.exe
...
BISECT: running pass (193) Tail Duplication on function (sum)
BISECT: running pass (194) Machine Copy Propagation Pass on function (sum)
BISECT: running pass (195) Post RA top-down list latency scheduler on function
(sum)
BISECT: NOT running pass (196) Branch Probability Basic Block Placement on
function (sum)
BISECT: NOT running pass (197) X86 Execution Dependency Fix on function (sum)
...
5 + 3 = -nan
Let's look at ASM before and after POSTRAScheduler:
=== nice-194.s
cvtsi2ssl %eax, %xmm0
movq8(%esp), %mm0
emms
punpckhdq %mm0, %mm0 # mm0 = mm0[1,1]
movd%mm0, %ecx
cvtsi2ssl %ecx, %xmm1
===
POSTRAScheduler changed order of operations to:
=== nice-195.s
movq8(%esp), %mm0
punpckhdq %mm0, %mm0 # mm0 = mm0[1,1]
movd%mm0, %ecx
emms
cvtsi2ssl %eax, %xmm0
cvtsi2ssl %ecx, %xmm1
===
So now emms is placed before mmx operation, and as a result, we receive wrong
answer.
--
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] Issue 5446 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-17 Type: Bug New issue 5446 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5446 Detailed report: https://oss-fuzz.com/testcase?key=4577867338874880 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: getMinSignedBits() <= 64 && "Too many bits for int64_t" llvm::APInt::getSExtValue llvm::BasicAAResult::DecomposeGEPExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710300453:201710310454 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4577867338874880 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
