[llvm-bugs] Issue 4018 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, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-11-02 New issue 4018 by monor...@clusterfuzz-external.iam.gserviceaccount.com: 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=4018 Detailed report: https://oss-fuzz.com/testcase?key=5649354464428032 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" AddressingModeMatcher::matchAddr AddressingModeMatcher::matchOperationAddr 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=5649354464428032 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 35166] New: GOMP interface for cancellation
https://bugs.llvm.org/show_bug.cgi?id=35166 Bug ID: 35166 Summary: GOMP interface for cancellation Product: OpenMP Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: pro...@itc.rwth-aachen.de CC: llvm-bugs@lists.llvm.org Latest GNU compiler generates code for cancellation. What is the reason to have the following assertion in kmp_gsupport.cpp? if(__kmp_omp_cancellation) KMP_FATAL(NoGompCancellation); -- 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 35128] inaccessiblememonly and inaccessiblemem_or_argmemonly overwrite does not work on call with operand bundle
https://bugs.llvm.org/show_bug.cgi?id=35128 Yichao Yu changed: What|Removed |Added Fixed By Commit(s)||317201 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 34653] [X86][AVX512] simple test crashes on assertion when targeting AVX512 with -O0
https://bugs.llvm.org/show_bug.cgi?id=34653 Ayman Musa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Ayman Musa --- Committed in https://reviews.llvm.org/rL317206 -- 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 35156] IR verification failed
https://bugs.llvm.org/show_bug.cgi?id=35156 Alexey Bataev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||a.bat...@hotmail.com --- Comment #1 from Alexey Bataev --- Fixed in r317208 -- 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 34887] [CodeGen][ExpandMemcmp] Regression on memcmp(p1, p2, N) lowering for N={16, 32} (X86)
https://bugs.llvm.org/show_bug.cgi?id=34887 Clement Courbet changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Clement Courbet --- Indeed. I assumed "Fixes PR34887" would magically close the bug :( -- 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 35167] New: Merge r309875 into the 5.0 branch: Move lock acquire/release functions in task deque cleanup code
https://bugs.llvm.org/show_bug.cgi?id=35167 Bug ID: 35167 Summary: Merge r309875 into the 5.0 branch: Move lock acquire/release functions in task deque cleanup code Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: hah...@hahnjo.de CC: andrey.churba...@intel.com, jpeyto...@gmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 The original locations can be reached without initializing the lock variable (td_deque_lock), so it is potentially unsafe. It is guaranteed that the lock is initialized if the deque (td_deque) is not NULL, and lock functions can be safely called. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35168] New: Merge r311269 into 5.0 branch: Use va_copy instead of __va_copy to fix building libomp against musl libc
https://bugs.llvm.org/show_bug.cgi?id=35168 Bug ID: 35168 Summary: Merge r311269 into 5.0 branch: Use va_copy instead of __va_copy to fix building libomp against musl libc Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: hah...@hahnjo.de CC: andrey.churba...@intel.com, jpeyto...@gmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 Fixes https://bugs.llvm.org/show_bug.cgi?id=34040 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35169] New: Merge r316452 into 5.0 branch: Disable threadprivate data cleanup if runtime is terminating
https://bugs.llvm.org/show_bug.cgi?id=35169 Bug ID: 35169 Summary: Merge r316452 into 5.0 branch: Disable threadprivate data cleanup if runtime is terminating Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: hah...@hahnjo.de CC: andrey.churba...@intel.com, jpeyto...@gmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 The problem is due to the runtime's threadprivate cleanup code which tries to access data that was already destroyed by one of the root threads. __kmp_init_gtid is used as a checker here since it is set to false before actual resource cleanup is done in __kmp_cleanup(). Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35170] New: Auto-vectorization is too aggressive/naive about scatter/gather instructions
https://bugs.llvm.org/show_bug.cgi?id=35170 Bug ID: 35170 Summary: Auto-vectorization is too aggressive/naive about scatter/gather instructions Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: Loop Optimizer Assignee: unassignedb...@nondot.org Reporter: d...@znu.io CC: llvm-bugs@lists.llvm.org Note: LLVM r317088 clang+llvm ToT built itself and -march=knl is way too aggressive/naive about using vector scatter/gather instructions during auto-vectorization. For example, consider llvm::DenseMap<...>::grow(unsigned int) [with code gen below). This generates a large loop that moves a ton of scalars and pointers from the scalar domain into the vector domain, packs said scalars, and then uses vpscatterqq to store the scalars as scalars. If the vector scatter/gather instructions were magically more efficient than the scalar equivalents, then maybe all of the scalar-to-vector copying and packing would be worth it -- but they're not. The scatter/gather instructions exist to *avoid* movement of data between the scalar and vector domains (like what the compiler generated): 1068530: 48 8d 8a 10 fe ff fflea-0x1f0(%rdx),%rcx 1068537: 48 8d 9a 20 fe ff fflea-0x1e0(%rdx),%rbx 106853e: 48 8d aa 30 fe ff fflea-0x1d0(%rdx),%rbp 1068545: 48 8d ba 40 fe ff fflea-0x1c0(%rdx),%rdi 106854c: 4c 8d 82 50 fe ff fflea-0x1b0(%rdx),%r8 1068553: 4c 8d b2 60 fe ff fflea-0x1a0(%rdx),%r14 106855a: 4c 8d 8a 70 fe ff fflea-0x190(%rdx),%r9 1068561: 4c 8d 92 80 fe ff fflea-0x180(%rdx),%r10 1068568: c4 c1 f9 6e ca vmovq %r10,%xmm1 106856d: c4 c1 f9 6e d1 vmovq %r9,%xmm2 1068572: c5 e9 6c c9 vpunpcklqdq %xmm1,%xmm2,%xmm1 1068576: c4 c1 f9 6e d6 vmovq %r14,%xmm2 106857b: c4 c1 f9 6e d8 vmovq %r8,%xmm3 1068580: c5 e1 6c d2 vpunpcklqdq %xmm2,%xmm3,%xmm2 1068584: c4 e3 6d 38 c9 01 vinserti128 $0x1,%xmm1,%ymm2,%ymm1 106858a: c4 e1 f9 6e d7 vmovq %rdi,%xmm2 106858f: c4 e1 f9 6e dd vmovq %rbp,%xmm3 1068594: c5 e1 6c d2 vpunpcklqdq %xmm2,%xmm3,%xmm2 1068598: c4 e1 f9 6e db vmovq %rbx,%xmm3 106859d: c4 e1 f9 6e e1 vmovq %rcx,%xmm4 10685a2: c5 d9 6c db vpunpcklqdq %xmm3,%xmm4,%xmm3 10685a6: c4 e3 65 38 d2 01 vinserti128 $0x1,%xmm2,%ymm3,%ymm2 10685ac: 62 f3 ed 48 3a c9 01vinserti64x4 $0x1,%ymm1,%zmm2,%zmm1 10685b3: 4c 8d 82 90 fe ff fflea-0x170(%rdx),%r8 10685ba: 4c 8d 8a a0 fe ff fflea-0x160(%rdx),%r9 10685c1: 4c 8d 92 b0 fe ff fflea-0x150(%rdx),%r10 10685c8: 4c 8d b2 c0 fe ff fflea-0x140(%rdx),%r14 10685cf: 48 8d 8a d0 fe ff fflea-0x130(%rdx),%rcx 10685d6: 48 8d ba e0 fe ff fflea-0x120(%rdx),%rdi 10685dd: 48 8d aa f0 fe ff fflea-0x110(%rdx),%rbp 10685e4: 48 8d 9a 00 ff ff fflea-0x100(%rdx),%rbx 10685eb: c4 e1 f9 6e d3 vmovq %rbx,%xmm2 10685f0: c4 e1 f9 6e dd vmovq %rbp,%xmm3 10685f5: c5 e1 6c d2 vpunpcklqdq %xmm2,%xmm3,%xmm2 10685f9: c4 e1 f9 6e df vmovq %rdi,%xmm3 10685fe: c4 e1 f9 6e e1 vmovq %rcx,%xmm4 1068603: c5 d9 6c db vpunpcklqdq %xmm3,%xmm4,%xmm3 1068607: c4 e3 65 38 d2 01 vinserti128 $0x1,%xmm2,%ymm3,%ymm2 106860d: c4 c1 f9 6e de vmovq %r14,%xmm3 1068612: c4 c1 f9 6e e2 vmovq %r10,%xmm4 1068617: c5 d9 6c db vpunpcklqdq %xmm3,%xmm4,%xmm3 106861b: c4 c1 f9 6e e1 vmovq %r9,%xmm4 1068620: c4 c1 f9 6e e8 vmovq %r8,%xmm5 1068625: c5 d1 6c e4 vpunpcklqdq %xmm4,%xmm5,%xmm4 1068629: c4 e3 5d 38 db 01 vinserti128 $0x1,%xmm3,%ymm4,%ymm3 106862f: 62 f3 e5 48 3a d2 01vinserti64x4 $0x1,%ymm2,%zmm3,%zmm2 1068636: 4c 8d 82 10 ff ff fflea-0xf0(%rdx),%r8 106863d: 4c 8d 8a 20 ff ff fflea-0xe0(%rdx),%r9 1068644: 4c 8d 92 30 ff ff fflea-0xd0(%rdx),%r10 106864b: 4c 8d b2 40 ff ff fflea-0xc0(%rdx),%r14 1068652: 48 8d 8a 50 ff ff fflea-0xb0(%rdx),%rcx 1068659: 48 8d ba 60 ff ff fflea-0xa0(%rdx),%rdi 1068660: 48 8d aa 70 ff ff fflea-0x90(%rdx),%rbp 1068667: 48 8d 5a 80 lea-0x80(%rdx),%rbx 106866b: c4 e1 f9 6e db vmovq %rbx,%xmm3 1068670: c4 e1 f9 6e e5 vmovq %rbp,%xmm4 1068675: c5 d9 6c db vpunpcklqdq %xmm3,%xmm4,%xmm3 1068679: c4 e1 f
[llvm-bugs] [Bug 35171] New: Merge r317115 into the 5.0 branch: Fix race condition in omp_init_lock
https://bugs.llvm.org/show_bug.cgi?id=35171 Bug ID: 35171 Summary: Merge r317115 into the 5.0 branch: Fix race condition in omp_init_lock Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: hah...@hahnjo.de CC: andrey.churba...@intel.com, jpeyto...@gmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 This is a partial fix for bug 34050. This prevents callers of omp_set_lock (which does not hold __kmp_global_lock) from ever seeing an uninitialized version of __kmp_i_lock_table.table. It does not solve a use-after-free race condition if omp_set_lock obtains a pointer to __kmp_i_lock_table.table before it is updated and then attempts to dereference afterwards. That race is far less likely and can be handled in a separate patch. The unit test usually segfaults on the current trunk revision. It passes with the patch. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35172] New: InMemoryFileSystem: Expose status (type and mode), allow specifying in addFile()
https://bugs.llvm.org/show_bug.cgi?id=35172 Bug ID: 35172 Summary: InMemoryFileSystem: Expose status (type and mode), allow specifying in addFile() Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: bgertzfi...@gmail.com CC: llvm-bugs@lists.llvm.org There's a FIXME in InMemoryFileSystem::addFile(): // FIXME: expose the status details in the interface. This means we cannot write tests which depend on the type or mode of the file, which is stored in the Status object. We should update the addFile() API to take an optional Status object (defaulting to regular file, all_all 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 35173] New: wrong code with opt "-sroa -early-cse -newgvn"
https://bugs.llvm.org/show_bug.cgi?id=35173
Bug ID: 35173
Summary: wrong code with opt "-sroa -early-cse -newgvn"
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: s...@cs.ucdavis.edu
CC: llvm-bugs@lists.llvm.org
Tested with trunk rev. 317206.
$ clangpolly -v
clang version 6.0.0 (http://llvm.org/git/clang.git
7366f8e06093256082548af7d4e7d3baf7bfeb83) (llvm/trunk 317141)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.3.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.2.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$
$ clangpolly -O0 small.c; ./a.out
$
$ clangpolly -O3 -mllvm -disable-llvm-optzns -c -emit-llvm -o small.bc -w
small.c
$ optpolly -sroa -early-cse -newgvn -o small-opt.bc small.bc
$ clangpolly small-opt.bc
$ ./a.out
Floating point exception (core dumped)
$
--
int a, c, f;
long b, e;
short d;
int main ()
{
if (c)
goto L1;
while (1)
{
int h = -1;
L2:{
int j = 0;
L1:
e = d ^ (h | (j & b));
a = a / ~(3 | ~e);
if (e)
break;
}
h = 0;
}
if (f)
goto L2;
return 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 35174] New: clang-cl "cannot mangle this built-in __float128 type" due to promotions
https://bugs.llvm.org/show_bug.cgi?id=35174
Bug ID: 35174
Summary: clang-cl "cannot mangle this built-in __float128 type"
due to promotions
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: h...@chromium.org
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk, r...@google.com
$ cat /tmp/a.cc
template struct B;
template constexpr bool is_floating_point_v = false;
struct StrictNumeric {
StrictNumeric(int);
template > = nullptr> operator
Dst();
};
static_assert(StrictNumeric(1) > 0);
$ bin/clang -cc1 -triple i686-pc-win32 /tmp/a.cc -std=c++17 -emit-obj
error: cannot mangle this built-in __float128 type yet
/tmp/a.cc:9:32: error: invalid operands to binary expression ('StrictNumeric'
and 'int')
static_assert(StrictNumeric(1) > 0);
^ ~
2 errors generated.
Note that the source never mentions __float128, but Clang tries to use it when
it tries to find a conversion of the StrictNumeric that works with the >
expression. In the process, it instantiates is_floating_point_v<__float128>,
causing the mangling error.
Should BuiltinOperatorOverloadBuilder::addGenericBinaryArithmeticOverloads()
only consider types that are valid for the target?
(We hit this in Chromium with the latest MS SDK; see http://crbug.com/780311)
--
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 35175] New: Merge r309288 into the 5.0 branch: Fix double destruction of objects when OpenMP construct is canceled
https://bugs.llvm.org/show_bug.cgi?id=35175 Bug ID: 35175 Summary: Merge r309288 into the 5.0 branch: Fix double destruction of objects when OpenMP construct is canceled Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 When an omp for loop is canceled the constructed objects are being destructed twice. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35176] New: Merge r310850 into the 5.0 branch: Fix for PR33676: Debug info for OpenMP region is broken.
https://bugs.llvm.org/show_bug.cgi?id=35176 Bug ID: 35176 Summary: Merge r310850 into the 5.0 branch: Fix for PR33676: Debug info for OpenMP region is broken. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 After some changes in clang/LLVM debug info for task-based regions was not generated at all. Patch fixes this problem. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35177] New: Merge r311013 into the 5.0 branch: Fix for PR28581: OpenMP linear clause - wrong results.
https://bugs.llvm.org/show_bug.cgi?id=35177 Bug ID: 35177 Summary: Merge r311013 into the 5.0 branch: Fix for PR28581: OpenMP linear clause - wrong results. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 If worksharing construct has at least one linear item, an implicit synchronization point must be emitted to avoid possible conflict with the loading/storing values to the original variables. Added implicit barrier if the linear item is found before actual start of the worksharing construct. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35178] New: Merge r311777 into the 5.0 branch: Fix for PR34321: ustom OpenMP reduction in C++ template causes SEGFAULT at compile time
https://bugs.llvm.org/show_bug.cgi?id=35178 Bug ID: 35178 Summary: Merge r311777 into the 5.0 branch: Fix for PR34321: ustom OpenMP reduction in C++ template causes SEGFAULT at compile time Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 Compiler crashed when tried to rebuild non-template expression in dependent context. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35179] New: Merge r312292, r312296 into the 5.0 branch: Fix for PR34398: assert with random access iterator if the step>1.
https://bugs.llvm.org/show_bug.cgi?id=35179 Bug ID: 35179 Summary: Merge r312292, r312296 into the 5.0 branch: Fix for PR34398: assert with random access iterator if the step>1. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 If the loop is a loot with random access iterators and the iteration construct is represented it += n, then the compiler crashed because of reusing of the same MaterializedTemporaryExpr around N. Patch fixes it by using the expression as written, without any special kind of wrappings. Note: I'm not really sure if we should merge this one: It touches quite a few tests and needs the second commit to fix the test. Just marking this for discussion, feel free to close if we don't want to merge it. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35180] New: Merge r313675 into the 5.0 branch: fix seg-faults printing diagnostics with invalid ordered(n) values
https://bugs.llvm.org/show_bug.cgi?id=35180 Bug ID: 35180 Summary: Merge r313675 into the 5.0 branch: fix seg-faults printing diagnostics with invalid ordered(n) values Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 When the value specified for n in ordered(n) is larger than the number of loops a segmentation fault can occur in one of two ways when attempting to print out a diagnostic for an associated depend(sink : vec): 1) The iteration vector vec contains less than n items 2) The iteration vector vec contains a variable that is not a loop control variable This patch addresses both of these issues. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35181] New: Merge r315464 into the 5.0 branch: Fix PR34916: Crash on mixing taskloop|tasks directives.
https://bugs.llvm.org/show_bug.cgi?id=35181 Bug ID: 35181 Summary: Merge r315464 into the 5.0 branch: Fix PR34916: Crash on mixing taskloop|tasks directives. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 If both taskloop and task directives are used at the same time in one program, we may ran into the situation when the particular type for task directive is reused for taskloop directives. Patch fixes this problem. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35182] New: Merge r315578 into the 5.0 branch: Fix PR34925: Fix getting thread_id lvalue for inlined regions in C.
https://bugs.llvm.org/show_bug.cgi?id=35182 Bug ID: 35182 Summary: Merge r315578 into the 5.0 branch: Fix PR34925: Fix getting thread_id lvalue for inlined regions in C. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 If we try to get the lvalue for thread_id variables in inlined regions, we did not use the correct version of function. Fixed this bug by adding overrided version of the function getThreadIDVariableLValue for inlined regions. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35183] New: Merge r315586 into the 5.0 branch: Fix PR34926: Fix handling of the array sections passed as function params.
https://bugs.llvm.org/show_bug.cgi?id=35183 Bug ID: 35183 Summary: Merge r315586 into the 5.0 branch: Fix PR34926: Fix handling of the array sections passed as function params. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 Codegen could crash if the array section base expression is the function parameter. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35184] New: Merge r315611 into the 5.0 branch: Fix PR34927: Emit initializer for reduction array with declare reduction.
https://bugs.llvm.org/show_bug.cgi?id=35184 Bug ID: 35184 Summary: Merge r315611 into the 5.0 branch: Fix PR34927: Emit initializer for reduction array with declare reduction. Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: hah...@hahnjo.de CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 34492 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35152] `Scope.hasEHBranches() == (EHEntry != nullptr)' assertion with openmp reproducer:
https://bugs.llvm.org/show_bug.cgi?id=35152 Alexey Bataev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Alexey Bataev --- Fixed in r317227 -- 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 35185] New: Merge r310522 into the 5.0 branch : [Linker] PR33527 - Linker::LinkOnlyNeeded should import AppendingLinkage globals
https://bugs.llvm.org/show_bug.cgi?id=35185 Bug ID: 35185 Summary: Merge r310522 into the 5.0 branch : [Linker] PR33527 - Linker::LinkOnlyNeeded should import AppendingLinkage globals Product: new-bugs Version: 5.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: zhen@autodesk.com CC: llvm-bugs@lists.llvm.org Blocks: 34492 Is it OK to merge the following revision(s) to the 5.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=34492 [Bug 34492] [meta] 5.0.1 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 35186] New: Merge r313776 into the 5.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35186 Bug ID: 35186 Summary: Merge r313776 into the 5.0 branch Product: new-bugs Version: 5.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: brian.c...@gmail.com CC: llvm-bugs@lists.llvm.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 35187] New: Clang regression tests fail on Windows when git “core.autocrlf” is set to true
https://bugs.llvm.org/show_bug.cgi?id=35187 Bug ID: 35187 Summary: Clang regression tests fail on Windows when git “core.autocrlf” is set to true Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: zhen@autodesk.com CC: llvm-bugs@lists.llvm.org The following clang regression tests fail on Windows when git “core.autocrlf” is set to true. Failing Tests (51): Clang :: ARCMT/designated-init-in-header/designated-init-in-header.m Clang :: ARCMT/objcmt-arc-cf-annotations.m Clang :: ARCMT/objcmt-atomic-property.m Clang :: ARCMT/objcmt-migrate-all.m Clang :: ARCMT/objcmt-ns-macros.m Clang :: ARCMT/objcmt-ns-nonatomic-iosonly.m Clang :: ARCMT/objcmt-property-availability.m Clang :: ARCMT/objcmt-property.m Clang :: ARCMT/objcmt-undefined-ns-macros.m Clang :: ARCMT/whitelisted/objcmt-with-whitelist-impl.m Clang :: ARCMT/whitelisted/objcmt-with-whitelist.m Clang :: CodeGen/debug-info-file-checksum.c Clang :: Driver/at_file.c Clang :: Format/xmloutput.cpp Clang :: Frontend/system-header-line-directive.c Clang :: Index/cxx11-lambdas.cpp Clang :: Index/get-cursor.cpp Clang :: Index/index-templates.cpp Clang :: Index/pch-opaque-value.cpp Clang :: Index/retain-comments-from-system-headers.c Clang :: Index/usrs.cpp Clang :: Index/usrs.m Clang :: Lexer/conflict-marker.c Clang :: Lexer/eof-conflict-marker.c Clang :: Modules/preprocess-module.cpp Clang :: PCH/preamble.c Clang :: Preprocessor/line-directive-output.c Clang :: Preprocessor/pp-modules.c Clang :: Preprocessor/pragma_sysheader.c Clang :: Preprocessor/print_line_empty_file.c Clang :: Preprocessor/print_line_include.c Clang :: Preprocessor/traditional-cpp.c Clang :: clang-rename/ClassAsTemplateArgument.cpp Clang :: clang-rename/ClassSimpleRenaming.cpp Clang :: clang-rename/ClassTestMulti.cpp Clang :: clang-rename/ComplexFunctionOverride.cpp Clang :: clang-rename/ComplicatedClassType.cpp Clang :: clang-rename/Ctor.cpp Clang :: clang-rename/CtorInitializer.cpp Clang :: clang-rename/DeclRefExpr.cpp Clang :: clang-rename/Field.cpp Clang :: clang-rename/FunctionMacro.cpp Clang :: clang-rename/FunctionOverride.cpp Clang :: clang-rename/InvalidOffset.cpp Clang :: clang-rename/MemberExprMacro.cpp Clang :: clang-rename/TemplateClassInstantiation.cpp Clang :: clang-rename/TemplateTypename.cpp Clang :: clang-rename/UserDefinedConversion.cpp Clang :: clang-rename/Variable.cpp Clang :: clang-rename/VariableMacro.cpp Clang :: clang-rename/YAMLInput.cpp I am working on a patch for this. -- 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 17537] Explicit specialization of deleted function template not possible
https://bugs.llvm.org/show_bug.cgi?id=17537 Andrew Somerville changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Andrew Somerville --- After testing in 3.9 and 5.0 I'm marking this fixed. Not sure if that's welcome from an outsider, but given this hasn't had any attention in a while, and the answer seems to be correct, seems appropriate. -- 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 31268] Umbrella: debug info for optimized code
https://bugs.llvm.org/show_bug.cgi?id=31268 Bug 31268 depends on bug 35015, which changed state. Bug 35015 Summary: Optimized code debug info: loop induction variable becomes constant https://bugs.llvm.org/show_bug.cgi?id=35015 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 35015] Optimized code debug info: loop induction variable becomes constant
https://bugs.llvm.org/show_bug.cgi?id=35015
Adrian Prantl changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED|RESOLVED
--- Comment #9 from Adrian Prantl ---
before:
0x009f: DW_TAG_variable
DW_AT_location(0x
0x0010 - 0x0032: DW_OP_consts +0,
DW_OP_stack_value)
DW_AT_name("i")
DW_AT_decl_file ("/tmp/t.c")
DW_AT_decl_line (8)
DW_AT_type(cu + 0x006c "int")
after:
0x009f: DW_TAG_variable
DW_AT_location(0x
0x0010 - 0x0012: DW_OP_consts +0,
DW_OP_stack_value
0x0012 - 0x0023: DW_OP_reg3 RBX
0x0027 - 0x002e: DW_OP_reg3 RBX)
DW_AT_name("i")
DW_AT_decl_file ("/tmp/t.c")
DW_AT_decl_line (8)
DW_AT_type(cu + 0x006c "int")
--
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 32560] GlobalISel AArch64: s16 FPR: Assertion failed: (OrigTy.getSizeInBits() == NewTy.getSizeInBits() && "Types with difference size cannot be handled by the default " "mapping")
https://bugs.llvm.org/show_bug.cgi?id=32560 Quentin Colombet changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Quentin Colombet --- r317287 -- 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 35075] Assertion failure in clang::ento::MemRegion::getAsOffset
https://bugs.llvm.org/show_bug.cgi?id=35075 George Karpenkov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from George Karpenkov --- @Alexander try now, hopefully should be working with ToT. -- 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 35189] New: r314561/r314622 + NewGVN cause crash/build failure with LibreOffice
https://bugs.llvm.org/show_bug.cgi?id=35189 Bug ID: 35189 Summary: r314561/r314622 + NewGVN cause crash/build failure with LibreOffice Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: lukebe...@hotmail.com CC: llvm-bugs@lists.llvm.org Before r314561, I could build LibreOffice with the NewGVN. After r314561, clang would crash building the firebird module. After r314622, the build fails during the basic Unit Testing phase. Steps to reproduce: 1. $ git clone git://anongit.freedesktop.org/libreoffice/core 2. $ apt-get build-dep libreoffice 3. create file autogen.input with CC=clang and CXX=clang++ 4. ./autogen.sh && make ENVCFLAGS="-mllvm -enable-newgvn" ENVCFLAGSCXX="-mllvm -enable-newgvn" r314561 firebird crash: https://zerobin.net/?5f7ed7a18356ed5e#hGewdFYM+2Y72x5gaNxyZPQhqg05QOMSAsd1O/4x+Dc= r314622 build failure: https://zerobin.net/?1236b71707b52bbd#nAoCi5YyFGdyE86rz08t8NWUu+EvV+vwUHRfG0xt1bA= -- 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
