[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35977, which changed state. Bug 35977 Summary: Vector shift misoptimized with AVX512 https://bugs.llvm.org/show_bug.cgi?id=35977 What|Removed |Added Status|RESOLVED|REOPENED 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 35977] Vector shift misoptimized with AVX512
https://bugs.llvm.org/show_bug.cgi?id=35977 Simon Pilgrim changed: What|Removed |Added Resolution|FIXED |--- Fixed By Commit(s)||322644 Blocks||35804 Status|RESOLVED|REOPENED --- Comment #2 from Simon Pilgrim --- (In reply to Benjamin Kramer from comment #1) > It was r321085. Fixed in r322644. Reopening as r322644 should be merged into the 6.00 release branch. Thanks for the fix! 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 35995] New: Merge r322830 into the 5.0 branch: Add missing headers for Debug builds
https://bugs.llvm.org/show_bug.cgi?id=35995 Bug ID: 35995 Summary: Merge r322830 into the 5.0 branch: Add missing headers for Debug builds Product: OpenMP Version: unspecified Hardware: PC OS: Linux Status: ASSIGNED Severity: release blocker Priority: P Component: Runtime Library Assignee: h...@chromium.org Reporter: hah...@hahnjo.de CC: andrey.churba...@intel.com, gro...@us.ibm.com, llvm-bugs@lists.llvm.org Blocks: 35804 I just found that the Debug build of libomptarget was broken when using libc++. I went ahead and added the needed header to two files, please consider merging to release_60. According to CODE_OWNERS.txt, Andrey is in charge of the "OpenMP runtime library" although this initially didn't include libomptarget. I'm not sure how to handle this... 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35991, which changed state. Bug 35991 Summary: [lldb] Please backport LLDB test regression fixes to 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=35991 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 35991] [lldb] Please backport LLDB test regression fixes to 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35991 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED CC||h...@chromium.org Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- > r322081 [test] Fix tests to use more portable LLVM_ENABLE_ZLIB Merged in r322833. > r321932 [test] Use full PATH lookup for tools Merged in r322832. -- 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 35972, which changed state. Bug 35972 Summary: [X86] "Unexpected illegal type!" in LegalizeDAG.cpp https://bugs.llvm.org/show_bug.cgi?id=35972 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 35972] [X86] "Unexpected illegal type!" in LegalizeDAG.cpp
https://bugs.llvm.org/show_bug.cgi?id=35972 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Hans Wennborg --- Merged in r322835. -- 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 35995] Merge r322830 into the 6.0 branch: Add missing headers for Debug builds
https://bugs.llvm.org/show_bug.cgi?id=35995 Hans Wennborg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- Merged in r322837. -- 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 35995, which changed state. Bug 35995 Summary: Merge r322830 into the 6.0 branch: Add missing headers for Debug builds https://bugs.llvm.org/show_bug.cgi?id=35995 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 35996] New: asan_rt_conflict_test-1 segfaults
https://bugs.llvm.org/show_bug.cgi?id=35996 Bug ID: 35996 Summary: asan_rt_conflict_test-1 segfaults Product: compiler-rt Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: compiler-rt Assignee: unassignedb...@nondot.org Reporter: diana.pi...@linaro.org CC: llvm-bugs@lists.llvm.org I am seeing something like this while testing the 6.0.0 release on ARM, AArch64 and x86: FAIL: AddressSanitizer-aarch64-linux-dynamic :: TestCases/Linux/asan_rt_confict_test-1.cc (3574 of 4) TEST 'AddressSanitizer-aarch64-linux-dynamic :: TestCases/Linux/asan_rt_confict_test-1.cc' FAILED Script: -- /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/./bin/clang --driver-mode=g++ -fsanitize=address -mno-omit-leaf-frame-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -gline-tables-only /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm.src/projects/compiler-rt/test/asan/TestCases/Linux/asan_rt_confict_test-1.cc -o /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/compiler-rt/test/asan/AARCH64LinuxDynamicConfig/TestCases/Linux/Output/asan_rt_confict_test-1.cc.tmp env LD_PRELOAD=libclang_rt.asan-aarch64.so not /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/compiler-rt/test/asan/AARCH64LinuxDynamicConfig/TestCases/Linux/Output/asan_rt_confict_test-1.cc.tmp 2>&1 | FileCheck /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm.src/projects/compiler-rt/test/asan/TestCases/Linux/asan_rt_confict_test-1.cc -- Exit Code: 1 Command Output (stderr): -- /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-apm_64-build/rc1/llvm.src/projects/compiler-rt/test/asan/TestCases/Linux/asan_rt_confict_test-1.cc:13:11: error: expected string not found in input // CHECK: Your application is linked against incompatible ASan runtimes ^ :1:1: note: scanning from here Error: Segmentation fault (core dumped) ^ :1:3: note: possible intended match here Error: Segmentation fault (core dumped) ^ -- 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 35997] New: [ARM] -Wtautological-type-limit-compare in libcxx and libcxxabi tests
https://bugs.llvm.org/show_bug.cgi?id=35997 Bug ID: 35997 Summary: [ARM] -Wtautological-type-limit-compare in libcxx and libcxxabi tests Product: libc++ Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: diana.pi...@linaro.org CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com I'm getting ~1160 test failures in libcxx and libcxxabi while testing the 6.0.0 release on ARM. They all seem to be something like this: TEST 'libc++ :: std/utilities/utility/pairs/pair.astuple/pairs.by.type.pass.cpp' FAILED Command: ['/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase2/Release/llvmCore-6.0.0-rc1.install/usr/local/bin/clang++', '-o', '/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/libcxx/test/std/utilities/utility/pairs/pair.astuple/Output/pairs.by.type.pass.cpp.o', '-x', 'c++', '/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/std/utilities/utility/pairs/pair.astuple/pairs.by.type.pass.cpp', '-c', '-v', '-D_LIBCPP_DISABLE_AVAILABILITY', '-ftemplate-depth=270', '-Werror=thread-safety', '-std=c++2a', '-include', '/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/support/nasty_macros.hpp', '-nostdinc++', '-I/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/include', '-I/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/libcxx/include/c++build', '-D__STDC_FORMAT_MACROS', '-D__STDC_LIMIT_MACROS', '-D__STDC_CONSTANT_MACROS', '-I/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/support', '-DLIBCXX_FILESYSTEM_STATIC_TEST_ROOT="/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/std/experimental/filesystem/Inputs/static_test_env"', '-DLIBCXX_FILESYSTEM_DYNAMIC_TEST_ROOT="/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/libcxx/test/filesystem/Output/dynamic_env"', '-DLIBCXX_FILESYSTEM_DYNAMIC_TEST_HELPER="/usr/bin/python2.7 /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/support/filesystem_dynamic_test_helper.py"', '-D_LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER', '-Wall', '-Wextra', '-Werror', '-Wuser-defined-warnings', '-Wshadow', '-Wno-unused-command-line-argument', '-Wno-attributes', '-Wno-pessimizing-move', '-Wno-c++11-extensions', '-Wno-user-defined-literals', '-Wno-noexcept-type', '-Wno-aligned-allocation-unavailable', '-Wsign-compare', '-Wunused-variable', '-Wunused-parameter', '-Wunreachable-code', '-Wno-conversion', '-Wno-unused-local-typedef', '-Wno-#warnings', '-c'] Exit Code: 1 Standard Error: -- clang version 6.0.0 (tags/RELEASE_600/rc1) Target: armv7l-unknown-linux-gnueabihf Thread model: posix InstalledDir: /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase2/Release/llvmCore-6.0.0-rc1.install/usr/local/bin Found candidate GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/5 Found candidate GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/5.4.0 Found candidate GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/6 Found candidate GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/6.0.0 Selected GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/5.4.0 Candidate multilib: .;@m32 Selected multilib: .;@m32 "/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase2/Release/llvmCore-6.0.0-rc1.install/usr/local/bin/clang-6.0" -cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -discard-value-names -main-file-name pairs.by.type.pass.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu generic -target-abi aapcs-linux -mfloat-abi hard -fallow-half-arguments-and-returns -dwarf-column-info -debugger-tuning=gdb -v -coverage-notes-file /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase3/Release/llvmCore-6.0.0-rc1.obj/projects/libcxx/test/std/utilities/utility/pairs/pair.astuple/Output/pairs.by.type.pass.cpp.gcno -nostdinc++ -resource-dir /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/Phase2/Release/llvmCore-6.0.0-rc1.install/usr/local/lib/clang/6.0.0 -include /home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/rc1/llvm.src/projects/libcxx/test/support/nasty_macros.hpp -D _LIBCPP_DISABLE_AVAILABILITY -I /home/tcwg-buildslave/workspace
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35977, which changed state. Bug 35977 Summary: Vector shift misoptimized with AVX512 https://bugs.llvm.org/show_bug.cgi?id=35977 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 35977] Vector shift misoptimized with AVX512
https://bugs.llvm.org/show_bug.cgi?id=35977 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Hans Wennborg --- Ben looked and helped me re-generate the test on the branch. Merged in r322840. -- 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 35998] New: [AMDGPU][MC] 64-bit image atomics are not supported
https://bugs.llvm.org/show_bug.cgi?id=35998 Bug ID: 35998 Summary: [AMDGPU][MC] 64-bit image atomics are not supported 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 According with AMD documentation, "Image atomic operations are supported on 32- and 64-bit-per pixel surfaces" "For atomic operations, DMASK is set to the number of VGPRs (Dwords) to send to the texture unit. DMASK legal values for atomic image operations: 0x1 = 32-bit atomics except cmpswap. 0x3 = 32-bit atomic cmpswap. 0x3 = 64-bit atomics except cmpswap. 0xf = 64-bit atomic cmpswap." Currently assembler supports 32-bit atomics only. An example of a failed test: image_atomic_add v[5:6], v1, s[8:15] dmask:0x3 -- 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 35812] PowerPC: cmpxchg generates incorrect code for i16 and i8
https://bugs.llvm.org/show_bug.cgi?id=35812 Nemanja Ivanovic changed: What|Removed |Added Status|ASSIGNED|RESOLVED Fixed By Commit(s)||https://reviews.llvm.org/rL ||322372 Blocks||35804 Resolution|--- |FIXED --- Comment #4 from Nemanja Ivanovic --- This is fixed by a pair of commits: https://reviews.llvm.org/rL322767 https://reviews.llvm.org/rL322372 These two commits need to be merged into the 6.0 branch. Hans, are you able to do that or do I need to get further approval and commit it to the branch? 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 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35812, which changed state. Bug 35812 Summary: PowerPC: cmpxchg generates incorrect code for i16 and i8 https://bugs.llvm.org/show_bug.cgi?id=35812 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 35999] New: [AMDGPU][MC] Image atomics should support 3-element addresses
https://bugs.llvm.org/show_bug.cgi?id=35999 Bug ID: 35999 Summary: [AMDGPU][MC] Image atomics should support 3-element addresses 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 Currently assembler supports only 1-, 2- and 4-element addresses. 3-element addresses are also legal and should be supported. An example of a failed test: image_atomic_add v5, v[1:3], s[8:15] dmask:0x1 -- 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 36000] New: [AMDGPU][MC] Image dst/data size must match dmask and tfe
https://bugs.llvm.org/show_bug.cgi?id=36000 Bug ID: 36000 Summary: [AMDGPU][MC] Image dst/data size must match dmask and tfe Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org Currently assembler does not check that specified dst/data size matches dmask and tfe. For example, the following code should fail to assemble: image_loadv[4:6], v[237:240], s[28:35] dmask:0x1 image_loadv[4:5], v[237:240], s[28:35] dmask:0x7 image_loadv[4:6], v[237:240], s[28:35] dmask:0x1 tfe -- 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 36001] New: [AMDGPU][MC] r128 modifier of image instructions should affect SRSRC size
https://bugs.llvm.org/show_bug.cgi?id=36001 Bug ID: 36001 Summary: [AMDGPU][MC] r128 modifier of image instructions should affect SRSRC size 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 r128 modifier specifies 128-bit resource size when present (256-bit by default). This modifier should affect SRSRC size. An example of a failed test: image_atomic_add v5, v1, s[8:11] dmask:0x1 r128 The instruction shown above is how SP3 disassembles the code. Note: r128 is removed in GFX9 so this issue has low priority -- 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 35764] [AMDGPU][MC][GFX8][GFX9] Missing XNACK_MASK support
https://bugs.llvm.org/show_bug.cgi?id=35764 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Dmitry --- Closed by commit 322189: http://llvm.org/viewvc/llvm-project?rev=322189&view=rev -- 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 35771] [AMDGPU][MC][GFX9] Enable inline constants for SDWA operands
https://bugs.llvm.org/show_bug.cgi?id=35771 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Dmitry --- closed by commit 322655: http://llvm.org/viewvc/llvm-project?rev=322655&view=rev -- 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 36002] New: clang-format-6 combines two nearby defines
https://bugs.llvm.org/show_bug.cgi?id=36002
Bug ID: 36002
Summary: clang-format-6 combines two nearby defines
Product: clang
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: release blocker
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: m...@komzpa.net
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Created attachment 19705
--> https://bugs.llvm.org/attachment.cgi?id=19705&action=edit
pagc_api.h test file
6.0.0-svn321677-1~exp1
clang-format produces this change that merges OPEN_ALLOCATED_NAME into
PAGC_FILE_OPEN.
File from project PostGIS.
```
-#define PAGC_FILE_OPEN(HANDLE,FNAME,MODE,WHERE,RET) \
- if ( ( HANDLE = fopen( FNAME , \
- MODE ) ) == NULL ) { \
- RET_ERR1( "\nCan't open: %s\n" ,FNAME,WHERE,RET) ; \
- }
-
-#define OPEN_ALLOCATED_NAME(ALLOC_NAME,EXT,HANDLE,NAME,MODE,DS_SYS,WHERE,RET)
\
- if ( ( ALLOC_NAME = ds_alloc_file_name(DS_SYS,NAME,EXT) ) == NULL ) { \
- return RET ; \
- } \
- PAGC_FILE_OPEN(HANDLE,ALLOC_NAME,MODE,WHERE,RET)
-
-
+#define PAGC_FILE_OPEN(HANDLE, FNAME, MODE, WHERE, RET) \
+ if ((HANDLE = fopen(FNAME, MODE)) == NULL) \
+ { RET_ERR1("\nCan't open: %s\n", FNAME, WHERE, RET); } \
+\
+ #define OPEN_ALLOCATED_NAME( \
+ ALLOC_NAME, \
+ EXT, \
+ HANDLE, \
+ NAME, \
+ MODE, \
+ DS_SYS, \
+ WHERE, \
+ RET) if ((ALLOC_NAME = ds_alloc_file_name(DS_SYS, NAME, EXT)) == \
+NULL) \
+ { \
+ return RET; \
+ } \
+ PAGC_FILE_OPEN(HANDLE, ALLOC_NAME, MODE, WHERE, RET)
```
--
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 35997, which changed state. Bug 35997 Summary: [ARM] -Wtautological-type-limit-compare in libcxx and libcxxabi tests https://bugs.llvm.org/show_bug.cgi?id=35997 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 35997] [ARM] -Wtautological-type-limit-compare in libcxx and libcxxabi tests
https://bugs.llvm.org/show_bug.cgi?id=35997 Marshall Clow (home) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Marshall Clow (home) --- *** This bug has been marked as a duplicate of bug 35698 *** -- 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 36003] New: clang-cl: Support the new /external: flag and #pragma system_header
https://bugs.llvm.org/show_bug.cgi?id=36003 Bug ID: 36003 Summary: clang-cl: Support the new /external: flag and #pragma system_header Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: h...@chromium.org CC: llvm-bugs@lists.llvm.org, nicolaswe...@gmx.de See https://blogs.msdn.microsoft.com/vcblog/2017/12/13/broken-warnings-theory/ -- 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 33130] clang-format resets comment indentation before ifdefs
https://bugs.llvm.org/show_bug.cgi?id=33130 Mark Zeren changed: What|Removed |Added CC||mze...@vmware.com Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Mark Zeren --- Krasmir submitted this in r307795, which was included in 5. -- 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 36004] New: clang-format preprocessor indentation instability and trailing directive's off by one
https://bugs.llvm.org/show_bug.cgi?id=36004 Bug ID: 36004 Summary: clang-format preprocessor indentation instability and trailing directive's off by one Product: clang Version: 6.0 Hardware: All OS: All Status: NEW Severity: release blocker Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: mze...@vmware.com CC: djas...@google.com, kli...@google.com, krasi...@google.com, llvm-bugs@lists.llvm.org Blocks: 35804 r312125, which introduced preprocessor indentation, shipped with a known issue where "indentation of comments immediately before indented preprocessor lines is toggled on each run". There's a second issue where trailing directives may be indented incorrectly. Both issues have reviews out: https://reviews.llvm.org/D42036 https://reviews.llvm.org/D42035 I would prefer to do _something_ for the 6.0 release. Some options include: a) review and submit the patches above to trunk and then and merge to the release branch. b) revert the feature for 6.0, keeping it on trunk. c) document the known issues / mark the feature as experimental. 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 33838] [X86][MMX] Incorrect operand sizes for MMX instructions
https://bugs.llvm.org/show_bug.cgi?id=33838 Andrew V. Tischenko changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Andrew V. Tischenko --- It's fixed in rL321549. -- 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 33838, which changed state. Bug 33838 Summary: [X86][MMX] Incorrect operand sizes for MMX instructions https://bugs.llvm.org/show_bug.cgi?id=33838 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 36005] New: libunwind: Segfault at the end of _Unwind_Backtrace
https://bugs.llvm.org/show_bug.cgi?id=36005 Bug ID: 36005 Summary: libunwind: Segfault at the end of _Unwind_Backtrace Product: Runtime Libraries Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: other Assignee: unassignedb...@nondot.org Reporter: andrew.caldw...@metaswitch.com CC: llvm-bugs@lists.llvm.org # Headline libunwind miscalculates the length of the .eh_frame section and sometimes reads off the end of the containing segment, leading to segfaults and sadness. # Discovery We discovered this in a rust project at our company, the program would segfault deep in _Unwind_Backtrace but only in a few specific circumstances: * Compiling against the MUSL libc, which implies: * Static linking of all libraries * Using a static build of libunwind from LLVM (version 3.9) * Only one of our codebases * Attempts to reproduce in a more controlled environment have all failed * The codebase in question is **big** resulting in an 84Mb binary # Backtrace (courtesy of GDB + line number links reverse engineered... Rustc builds libunwind without debug symbols) ``` #0 0x00fa733b in libunwind::LocalAddressSpace::get32(unsigned long) () https://github.com/llvm-mirror/libunwind/blob/release_39/src/AddressSpace.hpp#L131 #1 0x00faa0a2 in libunwind::CFI_Parser::findFDE(libunwind::LocalAddressSpace&, unsigned long, unsigned long, unsigned int, unsigned long, libunwind::CFI_Parser::FDE_Info*, libunwind::CFI_Parser::CIE_Info*) () https://github.com/llvm-mirror/libunwind/blob/release_39/src/DwarfParser.hpp#L184 #2 0x00fa983d in libunwind::UnwindCursor::getInfoFromDwarfSection(unsigned long, libunwind::UnwindInfoSections const&, unsigned int) () https://github.com/llvm-mirror/libunwind/blob/release_39/src/UnwindCursor.hpp#L900 #3 0x00fa923d in libunwind::UnwindCursor::setInfoBasedOnIPRegister(bool) () https://github.com/llvm-mirror/libunwind/blob/release_39/src/UnwindCursor.hpp#L1241 #4 0x00fa8fff in libunwind::UnwindCursor::step() () #5 0x00fa820e in unw_step () #6 0x00fa6ac0 in _Unwind_Backtrace () ``` # Analysis * Looking at frame #1 it appears that, although `p < ehSectionEnd`, it points into invalid memory, playing around suggests that `ehSectionEnd` is massively beyond the range of readable memory. * Tracking back, we see that `ehSectionEnd` is `sects.dwarf_section_length` which is populated by the code at https://github.com/llvm-mirror/libunwind/blob/release_39/src/AddressSpace.hpp#L390-L441 (called from https://github.com/llvm-mirror/libunwind/blob/release_39/src/UnwindCursor.hpp#L1214). * This code is a little weird, and I'm not 100% it's doing anything sensible, but I've assumed it's doing the following: * Searching for a `LOAD` segment that contains the address we're interested in and remembering this segment's base address and length * Searching for a `GNU_EH_FRAME` segment, parsing it (assuming it contains exactly one `.eh_frame_ptr` section, which I guess is the spec for a segment of this type) to find the location of the `.eh_frame` section * Assuming that the `.eh_frame` points into the LOAD segment we found (not sure this is guaranteed, but maybe?) * Storing off the `.eh_frame` section's length by assuming it's the `LOAD` segment's `memsz` * This last bullet is where I think the bug lies, the `.eh_frame` is not always (never?) the first section in the `LOAD` segment, so the length of that section is strictly less than the size of the `LOAD` segment # Proposed fix Change https://github.com/llvm-mirror/libunwind/blob/release_39/src/AddressSpace.hpp#L434 to: cbdata->sects->dwarf_section_length = object_length - (cbdata->sects->dwarf_section - cbdata->sects->dso_base); This is better than the existing code (since the span from `cbdata->sects->dwarf_section` to `cbdata->sects->dwarf_section + cbdata->sects->dwarf_section_length` is all contained in the `LOAD` segment and is thus valid memory, but it's still not perfectly correct (as that span contains any sections after the `.eh_frame` section in the `LOAD` segment). I'm not sure there is a way to determine the end of a `.eh_frame` section, otherwise I'd recommend using that here. OTOH this change prevented the segfault I was seeing, without affecting backtrace generation. # Affected versions I found this on version 3.9, but the issue is still present in version 6.0 and seems to have been around since at least version 3.7 (and all versions in between). # Platform Linux Mint 18.1 Serena (based on Ubuntu 16.04 Xenial Xerus) on x86_64. Also seen on Centos 7 on x86_64. Segfaulting code compiled with Rustc version 1.22.0, 1.22.1, 1.23.0, 1.24.0-beta or 1.25.0-nightly. # Open Questions * Why doesn't this always crash? * Why do we only see this i
[llvm-bugs] [Bug 36006] New: lld: TEST 'lld :: COFF/manifestinput-error.test' is not recognized as unsupported in stand-alone
https://bugs.llvm.org/show_bug.cgi?id=36006 Bug ID: 36006 Summary: lld: TEST 'lld :: COFF/manifestinput-error.test' is not recognized as unsupported in stand-alone Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org Blocks: 35804 The lld test suite started failing at the following test: FAIL: lld :: COFF/manifestinput-error.test (108 of 1465) After some investigation, I was able to determine that the root cause of the failure is that... the test should not be run on my system at all, because of: # UNSUPPORTED: libxml2 This feature is supposed to be set based on the value of LLVM_LIBXML2_ENABLED. However, this variable is internal to LLVM itself and is not included in any CMake files installed. Therefore, it is not present when building stand-alone against installed LLVM. 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 36007] New: After r320749, Assertion failed: (!NodePtr->isKnownSentinel()), function operator*, file include/llvm/ADT/ilist_iterator.h, line 140.
https://bugs.llvm.org/show_bug.cgi?id=36007
Bug ID: 36007
Summary: After r320749, Assertion failed:
(!NodePtr->isKnownSentinel()), function operator*,
file include/llvm/ADT/ilist_iterator.h, line 140.
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: dimi...@andric.com
CC: llvm-bugs@lists.llvm.org
As reported in https://bugs.freebsd.org/225275, compiling the textproc/groonga
and www/nginx ports for armv6 asserts with:
Assertion failed: (!NodePtr->isKnownSentinel()), function operator*, file
include/llvm/ADT/ilist_iterator.h, line 140.
This regressed after https://reviews.llvm.org/rL320749, which is a fix for bug
34603.
Minimized test case:
/* clang -cc1 -triple armv6kz -S -target-cpu arm1176jzf-s -O2
ngx_inet-minimized.c */
int a;
int c() {
int b;
__asm("" : "+r"(b));
return b;
}
short d() {
switch (a) {
case 0:
return c();
case 1:
return 0;
default:
return c();
}
}
--
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 35958] [GlobalISel] CodeModel::Large sequences are not emitted
https://bugs.llvm.org/show_bug.cgi?id=35958 Amara Emerson changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Amara Emerson --- Fixed in r322878. -- 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 35831] After r315899, labels after x86 prefixes cause errors
https://bugs.llvm.org/show_bug.cgi?id=35831 Dimitry Andric changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Dimitry Andric --- Has been fixed by r322623, which was merged to the 6.0 branch 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 10988] x86 MC encoder and disassembler bugs umbrella
https://bugs.llvm.org/show_bug.cgi?id=10988 Bug 10988 depends on bug 35831, which changed state. Bug 35831 Summary: After r315899, labels after x86 prefixes cause errors https://bugs.llvm.org/show_bug.cgi?id=35831 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 36008] New: Regression (r316268): erroneous -Wsign-compare for typeof(enum T) and typeof(enumValue)
https://bugs.llvm.org/show_bug.cgi?id=36008
Bug ID: 36008
Summary: Regression (r316268): erroneous -Wsign-compare for
typeof(enum T) and typeof(enumValue)
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: arpha...@gmail.com
CC: llvm-bugs@lists.llvm.org
In LLVM 6 Clang reports -Wsign-compare:
comparison of integers of different signs: 'typeof (lhs)' (aka 'enum EnumTest')
and 'typeof (kValue)' (aka 'int')
For the following sample:
enum EnumTest {
kValue = 0,
};
void foo(enum EnumTest lhs) {
__typeof__(lhs) x = lhs;
__typeof__(kValue) y = kValue;
x == y;
}
This is a regression after r316268.
--
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 33281] Clang crash on invalid c++11 code (UNREACHABLE executed at clang/lib/AST/StmtProfile.cpp:1196!)
https://bugs.llvm.org/show_bug.cgi?id=33281 Vedant Kumar changed: What|Removed |Added Resolution|--- |WORKSFORME 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 36009] New: Setting VFP Flag on ELF binaries
https://bugs.llvm.org/show_bug.cgi?id=36009 Bug ID: 36009 Summary: Setting VFP Flag on ELF binaries Product: lld Version: unspecified Hardware: Other OS: FreeBSD Status: NEW Severity: enhancement Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: kev...@freebsd.org CC: llvm-bugs@lists.llvm.org Hi, We're working on linking the FreeBSD base system with LLD on ARMv7. We've discovered that LLD is not setting the VFP flag on the ELFs it's producing, which we need for rtld to use the hard-float libraries. Using -target armv7-gnueabihf-freebsd12.0 yields, as an example, the following: ELF Header: Magic: 7f 45 4c 46 01 01 01 09 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI:FreeBSD ABI Version: 0 Type: EXEC (Executable file) Machine: ARM Version: 0x1 Entry point address: 0x14000 Start of program headers: 52 (bytes into file) Start of section headers: 170068 (bytes into file) Flags: 0x500, Version5 EABI Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 11 Size of section headers: 40 (bytes) Number of section headers: 34 Section header string table index: 31 Hacking it in by OR'ing EF_ARM_VFP_FLOAT here: http://src.illumos.org/source/xref/freebsd-head/contrib/llvm/tools/lld/ELF/Arch/ARM.cpp#103 at least gives me a bootable system that works so far, but this is presumably not ideal. =) -- 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 36010] New: [X86] JMP16r/JMP32r missing from Sandy Bridge scheduler model
https://bugs.llvm.org/show_bug.cgi?id=36010 Bug ID: 36010 Summary: [X86] JMP16r/JMP32r missing from Sandy Bridge scheduler model Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: craig.top...@gmail.com CC: llvm-bugs@lists.llvm.org JMP64r is in the same group with the relative jumps, but the other two are missing. I kinda suspect JMP64r is incorrect. -- 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 36011] New: Incorrect codegen for x32 ?
https://bugs.llvm.org/show_bug.cgi?id=36011 Bug ID: 36011 Summary: Incorrect codegen for x32 ? Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: cs12b1...@iith.ac.in CC: llvm-bugs@lists.llvm.org Created attachment 19708 --> https://bugs.llvm.org/attachment.cgi?id=19708&action=edit test case Even though RBX is a callee-save register, it is not being saved before use in the "base()" function in the attached test case. I have checked with LLVM 3.8 too and the same behavior exists even then. It is reproducible on trunk Jan 18/2018. Steps to reproduce bug: llc -mtriple=x86_64-pc-linux-gnux32 -stackrealign -stack-alignment=32 final.ll clang final.s ./a.out echo $? Expected return value: 30 Actual return value: garbage. The test case is an extended version of x86-64-baseptr.ll -- 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
