[llvm-bugs] [Bug 36813] New: Merge r326235 into the 6.0 branch : [MinGW, CrossWindows] Allow passing -static together with -shared
https://bugs.llvm.org/show_bug.cgi?id=36813 Bug ID: 36813 Summary: Merge r326235 into the 6.0 branch : [MinGW, CrossWindows] Allow passing -static together with -shared Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org Blocks: 36649 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36814] New: Merge r326173 r326476 into the 6.0 branch : [RecordLayout] Don't align to non-power-of-2 sizes when using -mms-bitfields
https://bugs.llvm.org/show_bug.cgi?id=36814 Bug ID: 36814 Summary: Merge r326173 r326476 into the 6.0 branch : [RecordLayout] Don't align to non-power-of-2 sizes when using -mms-bitfields Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org Blocks: 36649 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36815] New: Merge r326172 into the 6.0 branch : [MinGW] Ignore the --start-group --end-group parameters
https://bugs.llvm.org/show_bug.cgi?id=36815 Bug ID: 36815 Summary: Merge r326172 into the 6.0 branch : [MinGW] Ignore the --start-group --end-group parameters Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org Blocks: 36649 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36816] New: Merge r327561 r327562 r327567 into the 6.0 branch : [COFF] Add support for the GNU ld flag --kill-at
https://bugs.llvm.org/show_bug.cgi?id=36816 Bug ID: 36816 Summary: Merge r327561 r327562 r327567 into the 6.0 branch : [COFF] Add support for the GNU ld flag --kill-at Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org Blocks: 36649 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36817] New: error: ‘sort’ is not a member of ‘llvm’
https://bugs.llvm.org/show_bug.cgi?id=36817 Bug ID: 36817 Summary: error: ‘sort’ is not a member of ‘llvm’ Product: lldb Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: ygolan...@isotek.co.uk CC: llvm-bugs@lists.llvm.org I am compiling LLVM from source (no packages for CentOS 7 which I use) and it compiles fine with ninja. However, when I add LLDB, I get the above error. I am 99% sure that this is something not right on my system, but I cannot fathom what it is. ``` ; uname -a Linux serval.isotek.co.uk 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ; ninja-build --version 1.7.2 ; gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux Thread model: posix gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ``` Here is the full stack trace: ``` ; ninja-build lldb [3/752] Building CXX object tools/lldb...es/lldbBreakpoint.dir/Breakpoint.cpp.o FAILED: tools/lldb/source/Breakpoint/CMakeFiles/lldbBreakpoint.dir/Breakpoint.cpp.o /usr/bin/c++ -DHAVE_ROUND -DLIBXML2_DEFINED -DLLDB_CONFIGURATION_DEBUG -DLLDB_USE_BUILTIN_DEMANGLER -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/lldb/source/Breakpoint -I/home/yann/src/llvm/tools/lldb/source/Breakpoint -Itools/lldb/include -I/home/yann/src/llvm/tools/lldb/include -I/usr/include/libxml2 -Iinclude -I/home/yann/src/llvm/include -I/usr/include/python2.7 -I/home/yann/src/llvm/tools/clang/include -Itools/lldb/../clang/include -I/home/yann/src/llvm/tools/lldb/source/. -fPIC -fvisibility-inlines-hidden -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing -Wno-deprecated-register -Wno-vla-extension -g -MD -MT tools/lldb/source/Breakpoint/CMakeFiles/lldbBreakpoint.dir/Breakpoint.cpp.o -MF tools/lldb/source/Breakpoint/CMakeFiles/lldbBreakpoint.dir/Breakpoint.cpp.o.d -o tools/lldb/source/Breakpoint/CMakeFiles/lldbBreakpoint.dir/Breakpoint.cpp.o -c /home/yann/src/llvm/tools/lldb/source/Breakpoint/Breakpoint.cpp /home/yann/src/llvm/tools/lldb/source/Breakpoint/Breakpoint.cpp: In member function ‘void lldb_private::Breakpoint::ModuleReplaced(lldb::ModuleSP, lldb::ModuleSP)’: /home/yann/src/llvm/tools/lldb/source/Breakpoint/Breakpoint.cpp:795:13: error: ‘sort’ is not a member of ‘llvm’ llvm::sort(old_id_vec.begin(), old_id_vec.end()); ^ /home/yann/src/llvm/tools/lldb/source/Breakpoint/Breakpoint.cpp:795:13: note: suggested alternative: In file included from /usr/include/c++/4.8.2/algorithm:62:0, from /home/yann/src/llvm/include/llvm/ADT/Optional.h:23, from /home/yann/src/llvm/include/llvm/ADT/STLExtras.h:20, from /home/yann/src/llvm/include/llvm/ADT/StringRef.h:13, from /home/yann/src/llvm/tools/lldb/include/lldb/lldb-priva
[llvm-bugs] [Bug 36524] [LV] Lost vectorization opportunity
https://bugs.llvm.org/show_bug.cgi?id=36524 Andrei Elovikov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||https://reviews.llvm.org/rL ||327960 -- 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 36195] Assertion `!hasScalarValue(Key, Instance) && "Scalar value already set"' failed.
https://bugs.llvm.org/show_bug.cgi?id=36195 Andrei Elovikov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||https://reviews.llvm.org/rL ||327960 -- 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 36817] error: ‘sort’ is not a member of ‘llvm’
https://bugs.llvm.org/show_bug.cgi?id=36817 lab...@google.com changed: What|Removed |Added CC||lab...@google.com Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from lab...@google.com --- There was a recent llvm refactor which introduced llvm::sort. Please make sure all your repositories llvm are synced to the same (latest) revision. If that doesn't help then, maybe you need to add some #include because the definition of llvm::sort is not being picked up for some reason. If that is the case, let me know, and I'll add the include. -- 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 36818] New: Checking provided compilation parameters
https://bugs.llvm.org/show_bug.cgi?id=36818 Bug ID: 36818 Summary: Checking provided compilation parameters Product: tools Version: 5.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: llvm-config Assignee: unassignedb...@nondot.org Reporter: markus.elfr...@web.de CC: llvm-bugs@lists.llvm.org The following software packages were installed also on my openSUSE Tumbleweed system. * GCC 7-2.9 * llvm5-devel 5.0.1-4.3 I have noticed the software situation that the command “llvm-config --cflags” can provide a compilation parameter which will trigger the message “cc: error: unrecognized command line option ‘-Wstring-conversion’; did you mean ‘-Wint-conversion’?”. Example: https://build.opensuse.org/package/show/openSUSE%3AFactory/smatch If I try another software build try out by a command like “make CC=clang …”, it can succeed. How should this configuration tool be improved? https://bugzilla.suse.com/show_bug.cgi?id=1082717 -- 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 36817] error: ‘sort’ is not a member of ‘llvm’
https://bugs.llvm.org/show_bug.cgi?id=36817 Yann Golanski changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #2 from Yann Golanski --- I updated everything and indeed that error is now fixed. Thank you. -- 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 36820] New: [InstCombine] simplifyAllocaArraySize fails for out of range constants
https://bugs.llvm.org/show_bug.cgi?id=36820
Bug ID: 36820
Summary: [InstCombine] simplifyAllocaArraySize fails for out of
range constants
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Common Code Generator Code
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: david.majne...@gmail.com, llvm-bugs@lists.llvm.org,
spatel+l...@rotateright.com
Reduced from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5223:
define void @f() {
BB:
%B51 = mul i864 65536, 65536
%B23 = sdiv i864 %B51, -1
%A9 = alloca i8, i864 %B23
br label %BB1
BB1: ; preds = %BB1, %BB
br i1 undef, label %BB1, label %BB3
BB3: ; preds = %BB3, %BB1
%G44 = getelementptr i8, i8* %A9, i1 undef
store i8* %G44, i8** undef
br label %BB3
}
--
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 36821] New: Timezones preference: default settinh
https://bugs.llvm.org/show_bug.cgi?id=36821 Bug ID: 36821 Summary: Timezones preference: default settinh Product: Bugzilla Admin Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Products Assignee: unassignedb...@nondot.org Reporter: dilyan.palau...@aegee.org CC: llvm-bugs@lists.llvm.org I think the most reasonable preference for the "Timezone used to display dates and times " setting users can have by default, unless they change it, is UTC. Currently it is "same as server" <=> PDT, and majority of world population cannot calculate the difference between their timezone and PDT. But the majority can calculate the distance between UTC and thier time zone. (Okay, this might not be a majority, but with any other combination there will be less people able to calculate the distance between their time and UTC, hence UTC is most suitable.) -- 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 36822] New: Email notification
https://bugs.llvm.org/show_bug.cgi?id=36822 Bug ID: 36822 Summary: Email notification Product: Bugzilla Admin Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: Mail Assignee: unassignedb...@nondot.org Reporter: dilyan.palau...@aegee.org CC: llvm-bugs@lists.llvm.org I have in my preferences When my relationship to this bug is: I want to receive mail when: AssigneeReporterCCed x x x A new bug is created Why haven't I received an email, when I created https://bugs.llvm.org/show_bug.cgi?id=36802 ? -- 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 4805 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: Deadline-Approaching Comment #4 on issue 4805 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4805#c4 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 15455] Incorrectly complains about `asm volatile("rep outsw %%es:(%%esi), (%%dx)" …`
https://bugs.llvm.org/show_bug.cgi?id=15455 Nirav Dave changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Nirav Dave --- This landed a while ago (r274152) -- 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 24308, which changed state. Bug 24308 Summary: assembler: suboptimal encoding of memory operand https://bugs.llvm.org/show_bug.cgi?id=24308 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 24308] assembler: suboptimal encoding of memory operand
https://bugs.llvm.org/show_bug.cgi?id=24308 Nirav Dave changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||nir...@google.com --- Comment #1 from Nirav Dave --- This appears to have been caused by not fully folding the constant in the address. Dumping to assembly results in vpaddd 12(%rdi,%rax), %xmm0, %xmm0 # encoding: [0xc5,0xf9,0xfe,0x44,0x07,0x0c] vpaddd 12(%rdi,%rax), %xmm0, %xmm0 # encoding: [0xc5,0xf9,0xfe,0x44,0x07,0x0c] vpaddd 12(%rdi,%rax), %xmm0, %xmm0 # encoding: [0xc5,0xf9,0xfe,0x44,0x07,0x0c] vpaddd 16-4(%rdi,%rax), %xmm0, %xmm0 # encoding:[0xc5,0xf9,0xfe,0x84,0x07,A,A,A,A] # fixup A - offset: 5, value: 16-4, kind: reloc_signed_4byte This was fixed after the 5 release sometime. -- 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 36811] Inline assembly input operand inefficiency
https://bugs.llvm.org/show_bug.cgi?id=36811 Nirav Dave changed: What|Removed |Added CC||nir...@google.com Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nirav Dave --- Currently llvm conservatively deals with "rm" as "m" to avoid running out of registers (PR8362). *** This bug has been marked as a duplicate of bug 35489 *** -- 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 35489] +g and +X inline asm constraints generate worse code than +r
https://bugs.llvm.org/show_bug.cgi?id=35489 Nirav Dave changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Nirav Dave --- jyknight found the original bug report. *** This bug has been marked as a duplicate of bug 20197 *** -- 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 36823] New: data race in lld/COFF/ICF.cpp
https://bugs.llvm.org/show_bug.cgi?id=36823 Bug ID: 36823 Summary: data race in lld/COFF/ICF.cpp Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: l...@inglorion.net CC: llvm-bugs@lists.llvm.org WARNING: ThreadSanitizer: data race (pid=46028) Write of size 8 at 0x7ba75f80 by thread T11: #0 __gnu_cxx::__normal_iterator > > std::__stable_partition_adaptive<__gnu_cxx::__normal_iterator > >, lld::coff::SectionChunk**, __gnu_cxx::__ops::_Iter_pred, long>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, __gnu_cxx::__ops::_Iter_pred, long, lld::coff::SectionChunk**, long) /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_algo.h:1572 (lld+0xe7c6d8) #1 __stable_partition<__gnu_cxx::__normal_iterator > >, __gnu_cxx::__ops::_Iter_pred<(lambda at /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:103:59)> > /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_algo.h:1626 (lld+0xe7a265) #2 stable_partition<__gnu_cxx::__normal_iterator > >, (lambda at /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:103:59)> /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_algo.h:1661 (lld+0xe7a265) #3 segregate /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:102 (lld+0xe7a265) #4 operator() /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:247 (lld+0xe7f45d) #5 _M_invoke /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:316 (lld+0xe7f45d) #6 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:706 (lld+0xe7d514) #7 forEachClassRange /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:185 (lld+0xe7d514) #8 operator() /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:205 (lld+0xe7d514) #9 operator() /usr/local/google/home/inglorion/llvm/llvm/include/llvm/Support/Parallel.h:179 (lld+0xe7d514) #10 _M_invoke /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:316 (lld+0xe7d514) #11 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:706 (lld+0xe89790) #12 operator() /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:134 (lld+0xe89790) #13 _M_invoke /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:316 (lld+0xe89790) #14 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:706 (lld+0xe88fa2) #15 work /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:111 (lld+0xe88fa2) #16 operator() /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:80 (lld+0xe890f3) #17 __invoke_impl /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/invoke.h:60 (lld+0xe890f3) #18 __invoke<(lambda at /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:80:21)> /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/invoke.h:95 (lld+0xe890f3) #19 _M_invoke<0> /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/thread:234 (lld+0xe890f3) #20 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/thread:243 (lld+0xe890f3) #21 _M_run /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/thread:186 (lld+0xe890f3) #22 std::error_code::default_error_condition() const ??:? (libstdc++.so.6+0xbc7e2) Previous read of size 8 at 0x7ba75f80 by thread T10: #0 findBoundary /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:173 (lld+0xe7d715) #1 forEachClassRange /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:181 (lld+0xe7d715) #2 operator() /usr/local/google/home/inglorion/llvm/lld/COFF/ICF.cpp:205 (lld+0xe7d715) #3 operator() /usr/local/google/home/inglorion/llvm/llvm/include/llvm/Support/Parallel.h:179 (lld+0xe7d715) #4 _M_invoke /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:316 (lld+0xe7d715) #5 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:706 (lld+0xe89790) #6 operator() /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:134 (lld+0xe89790) #7 _M_invoke /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:316 (lld+0xe89790) #8 operator() /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/std_function.h:706 (lld+0xe88fa2) #9 work /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:111 (lld+0xe88fa2) #10 operator() /usr/local/google/home/inglorion/llvm/llvm/lib/Support/Parallel.cpp:80 (lld+0xe890
[llvm-bugs] Issue 3638 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type
Comment #8 on issue 3638 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3638#c8 ClusterFuzz has detected this issue as fixed in range 201803190520:201803200524. Detailed report: https://oss-fuzz.com/testcase?key=4594987875434496 Project: llvm Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer Fuzz target binary: llvm-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe1f8a68e0 Crash State: char const* parse_type Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710131611:201710131923 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803190520:201803200524 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4594987875434496 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- 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 3640 in oss-fuzz: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer
Comment #8 on issue 3640 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3640#c8 ClusterFuzz has detected this issue as fixed in range 201803190520:201803200524. Detailed report: https://oss-fuzz.com/testcase?key=5505521747492864 Project: llvm Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer Fuzz target binary: llvm-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_llvm-demangle-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710131611:201710131923 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803190520:201803200524 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5505521747492864 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- 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 3638 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #9 on issue 3638 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3638#c9 ClusterFuzz testcase 4594987875434496 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- 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 3640 in oss-fuzz: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #9 on issue 3640 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3640#c9 ClusterFuzz testcase 5505521747492864 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- 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 36750] Meyers' singleton does not work with [[gnu::pure]] and -O1 to -O3
https://bugs.llvm.org/show_bug.cgi?id=36750 Eli Friedman changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|REOPENED --- Comment #7 from Eli Friedman --- s_myClass is a global variable, and myClass() modifies it, so it's not pure. At least, that's how it works from LLVM's perspective. If that doesn't actually match gcc's behavior, we could possibly change LLVM, I guess? But we'd need more evidence gcc actually implements a different rule. -- 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 7037 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseEncoding
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-03-20 Type: Bug New issue 7037 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7037 Detailed report: https://oss-fuzz.com/testcase?key=5661424173973504 Project: llvm Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer Fuzz target binary: llvm-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffcfebbaf00 Crash State: Db::parseEncoding Db::parseName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803190520:201803200524 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5661424173973504 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 36824] New: Merge r327863 into the 6.0 branch : [Driver] Avoid invalidated iterator in insertTargetAndModeArgs
https://bugs.llvm.org/show_bug.cgi?id=36824 Bug ID: 36824 Summary: Merge r327863 into the 6.0 branch : [Driver] Avoid invalidated iterator in insertTargetAndModeArgs Product: clang Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org Blocks: 36649 commit 3bd89a4b0543a84457046c08b80149b1c8d358f5 Author: Serge Pavlov Date: Mon Mar 19 17:13:43 2018 [Driver] Avoid invalidated iterator in insertTargetAndModeArgs Doing an .insert() can potentially invalidate iterators by reallocating the vector's storage. When all the stars align just right, this causes segfaults or glibc aborts. Gentoo Linux bug (crashes while building Chromium): https://bugs.gentoo.org/650082. Patch by Hector Martin! Differential Revision: https://reviews.llvm.org/D44607 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@327863 91177308-0d34-0410-b5e6-96231b3b80d8 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=36649 [Bug 36649] [meta] 6.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 36274] [m32][debug] "Wrong topological sorting" in ScheduleDAG.cpp after r324359
https://bugs.llvm.org/show_bug.cgi?id=36274 Nirav Dave changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nirav Dave --- Fixed in rL327898 -- 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 36312] clang crashes at -O1 and above: Assertion `Node2Index[SU.NodeNum] > Node2Index[PD.getSUnit()->NodeNum] && "Wrong topological sorting"' failed
https://bugs.llvm.org/show_bug.cgi?id=36312 Nirav Dave changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Nirav Dave --- Fixed in r327898. -- 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 17836] Assertion `Node2Index[SU->NodeNum] > Node2Index[I->getSUnit()->NodeNum] && "Wrong topological sorting"' failed.
https://bugs.llvm.org/show_bug.cgi?id=17836 Nirav Dave changed: What|Removed |Added Assignee|unassignedb...@nondot.org |nir...@google.com CC||nir...@google.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Nirav Dave --- These bugs are relatively finicky, and no longer happens at tup. Looking at the pre-ISEL SelectionDAG this looks like another missed bug infinally cycle dependencies and should have been resolved in r327898. -- 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 33869] Clang is not aware of a false dependency of LZCNT, TZCNT, POPCNT on destination register on some Intel CPUs
https://bugs.llvm.org/show_bug.cgi?id=33869
Ori Livneh changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED|REOPENED
--- Comment #24 from Ori Livneh ---
As far as I can tell, clang still does not break the dependency in the
reproduction case I attached in comment 14. Minimally:
#include
#include
__attribute__((noinline))
int msb(uint64_t n) {
return 63 ^ __builtin_clzll(n);
}
clang version 7.0.0 (trunk 327823), -O2 -march=haswell:
lzcnt rax, rdi
xor eax, 63
ret
g++ 8.0.1 20180319, -O2 -march=haswell:
xor eax, eax
lzcnt rax, rdi
xor eax, 63
ret
https://godbolt.org/g/JC57Ri
The failure to break the dependency chain causes a measurable degradation in
performance when the function is called in a loop. I tested on one Haswell
machine and one Broadwell machine.
Worse, clang is shooting itself in the foot. If you compile the same code but
target an older microarchitecture w/no lzcnt (-march=core-i7 for example),
clang emits a bsr instruction instead, which doesn't appear to suffer from this
false dependency issue.
--
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 28154] [meta] Add support for CodeView, the MSVC-compatible debug information format
https://bugs.llvm.org/show_bug.cgi?id=28154 Bug 28154 depends on bug 28458, which changed state. Bug 28458 Summary: [codeview] Emit variable scope information in -O0 builds https://bugs.llvm.org/show_bug.cgi?id=28458 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 28458] [codeview] Emit variable scope information in -O0 builds
https://bugs.llvm.org/show_bug.cgi?id=28458 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Reid Kleckner --- Brock fixed this in https://reviews.llvm.org/D42926, which eventually stuck as r327670. -- 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 36731] FastISel causes assertion "i8 shifts should be handled by autogenerated table"
https://bugs.llvm.org/show_bug.cgi?id=36731 Valentin Churavy 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 36649] [meta] 6.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=36649 Bug 36649 depends on bug 36731, which changed state. Bug 36731 Summary: FastISel causes assertion "i8 shifts should be handled by autogenerated table" https://bugs.llvm.org/show_bug.cgi?id=36731 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 36825] New: [PPC] if-converter triggers assertion `!NodePtr->isKnownSentinel()`
https://bugs.llvm.org/show_bug.cgi?id=36825 Bug ID: 36825 Summary: [PPC] if-converter triggers assertion `!NodePtr->isKnownSentinel()` Product: new-bugs Version: 6.0 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: v.chur...@gmail.com CC: llvm-bugs@lists.llvm.org Found while upgrading the Julia frontend to LLVM 6.0. ``` /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/include/llvm/ADT/ilist_iterator.h:140: llvm::ilist_iterator::reference llvm::ilist_iterator::operator*() const [with OptionsT = llvm::ilist_detail::node_options; bool IsReverse = false; bool IsConst = false; llvm::ilist_iterator::reference = llvm::MachineInstr&]: Assertion `!NodePtr->isKnownSentinel()' failed. signal (6): Aborted in expression starting at sysimg.jl:213 gsignal at /lib64/libc.so.6 (unknown line) abort at /lib64/libc.so.6 (unknown line) __assert_fail_base at /lib64/libc.so.6 (unknown line) __assert_fail at /lib64/libc.so.6 (unknown line) operator* at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/include/llvm/ADT/ilist_iterator.h:140 operator* at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/include/llvm/CodeGen/MachineInstrBundleIterator.h:134 [inlined] operator* at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/include/llvm/CodeGen/MachineInstrBundleIterator.h:179 [inlined] operator-> at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/include/llvm/CodeGen/MachineInstrBundleIterator.h:180 [inlined] IfConvertDiamondCommon at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/CodeGen/IfConversion.cpp:1726 IfConvertDiamond at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/CodeGen/IfConversion.cpp:1910 [inlined] runOnMachineFunction at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/CodeGen/IfConversion.cpp:461 runOnFunction at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/CodeGen/MachineFunctionPass.cpp:62 runOnFunction at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/IR/LegacyPassManager.cpp:1520 runOnModule at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/IR/LegacyPassManager.cpp:1541 run at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/IR/LegacyPassManager.cpp:1597 run at /raid1/home/ibm/valentin/src/julia/deps/srccache/llvm-6.0.0/lib/IR/LegacyPassManager.cpp:1731 operator() at /raid1/home/ibm/valentin/src/julia/src/jitlayers.cpp:466 Allocations: 43736398 (Pool: 43715287; Big: 2); GC: 111 ``` I am failing to isolate this failure for the last two weeks (also see http://lists.llvm.org/pipermail/llvm-dev/2018-March/121932.html) I nailed it down to the function `japi1__require_7687` (in gdb `MF->getName`) and I put the log online (124MB) https://drive.google.com/open?id=1Br0s9Qvr4tzPv8nqbnV_nWezpEH5Ci7B The setup of the target machine is roughly equivalent to: ``` llc -O3 -fast-isel=0 -code-model=medium -mcpu=pwr8 -relocation-model=static -emulated-tls ``` and the last Julia specific pass in the log is LowerPTLS. So a pipeline starting from `bool-ret-to-int` should be able to re-trigger the assertion, but to no avail. I compared the output of `debug-pass=Arguments` and the only difference between the pipeline used by `llc` and `julia` post `bool-ret-to-int` is: ``` llc: -basicaa -aa -loops -branch-prob -isel -machinedomtree -ppc-ctr-loops-verify -ppc-vsx-copy -expand-isel-pseudos Julia: -basicaa -aa -loops -branch-prob -machinedomtree -ppc-ctr-loops-verify -ppc-vsx-copy -expand-isel-pseudos ``` Note the additional `isel` in the llc pipeline that is missing in Julia, but I can't find a reason why that would be true. Some other breadcrumps: ``` Ifcvt: function (4486) 'japi1__require_7687' Ifcvt (Diamond): %bb.38 (T:44,F:39) (gdb) p BBI.BB->dump() %bb.38: derived from LLVM BB %L762 Live Ins: %x23 Predecessors according to CFG: %bb.37 renamable %x3 = LD 504, %x31; mem:Volatile LD8[%"#temp#15"](dereferenceable) dbg:loading.jl:1024 renamable %x4 = XORI8 renamable %x3, 1; dbg:loading.jl:1024 renamable %cr0 = CMPLDI renamable %x3, 1; dbg:loading.jl:1024 renamable %x4 = CNTLZD killed renamable %x4; dbg:loading.jl:1024 renamable %x4 = RLDICL killed renamable %x4, 58, 63; dbg:loading.jl:1024 STD killed renamable %x3, 1352, %x31; mem:ST8[%33] dbg:loading.jl:1024 STB renamable %r4, 1351, %x31, implicit killed %x4; mem:ST1[%34] dbg:loading.jl:1024 renamable %x3 = ADDIStocHA %x2, @"jl_global#10"; dbg:loading.jl:1024 renamable %x3 = LDtocL @"jl_global#10", killed renamable %x3, implicit %x2; mem:LD8[GOT] dbg:loading.jl:1024 Successors according to CFG: %bb.39(0x4000 / 0x8000 = 50.00%) %bb.44(0x4000 / 0x8000
[llvm-bugs] [Bug 36826] New: X86 should enable aggressive FMA formation (at least on skylake)
https://bugs.llvm.org/show_bug.cgi?id=36826
Bug ID: 36826
Summary: X86 should enable aggressive FMA formation (at least
on skylake)
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: chandl...@gmail.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org
On skylake, vector FP add has the same latency and throughput as FMA, so we
should definitely enable aggressive FMA formation.
On haswell and broadwell the issue is more complex. Add has shorter latency (3
cycles vs 5 cycles according to Agner) but half the throughput (one port rather
than two ports). I suspect that this is sufficient for it to be worth using FMA
everywhere, but we should benchmark to confirm.
If we can enable it everywhere, simply the following patch will suffice:
```
--- a/llvm/lib/Target/X86/X86ISelLowering.h
+++ b/llvm/lib/Target/X86/X86ISelLowering.h
@@ -838,6 +838,9 @@ namespace llvm {
return 2;
}
+/// Force aggressive FMA fusion.
+bool enableAggressiveFMAFusion(EVT VT) const override { return true; }
+
/// Return the value type to use for ISD::SETCC.
EVT getSetCCResultType(const DataLayout &DL, LLVMContext &Context,
EVT VT) const override;
```
Otherwise, we'll need to factor the per-subtarget facility for this out of the
AArch64 backend and use it to enable this on a per-subtarget basis for the X86
backend as well.
--
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 32325] [META][X86] Improve implementation and use of X86 scheduler models
https://bugs.llvm.org/show_bug.cgi?id=32325 Bug 32325 depends on bug 36808, which changed state. Bug 36808 Summary: [X86] PMULLD latency wrong in skylake scheduler model https://bugs.llvm.org/show_bug.cgi?id=36808 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 36808] [X86] PMULLD latency wrong in skylake scheduler model
https://bugs.llvm.org/show_bug.cgi?id=36808 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Craig Topper --- Fixed in r328061 -- 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 36827] New: [X86] SkylakeClient scheduler model doesn't know that client has less vector ALUs than server
https://bugs.llvm.org/show_bug.cgi?id=36827
Bug ID: 36827
Summary: [X86] SkylakeClient scheduler model doesn't know that
client has less vector ALUs than server
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: craig.top...@gmail.com
CC: llvm-bugs@lists.llvm.org
For example, skylake client only has 2 vector mutltipliers on ports 0 and 1.
But we have this in the scheduler model.
def SKLWriteResGroup49 : SchedWriteRes<[SKLPort015]> {
let Latency = 4;
let NumMicroOps = 1;
let ResourceCycles = [1];
}
def: InstRW<[SKLWriteResGroup49], (instregex "VPMADDUBSWYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMADDUBSWrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMADDWDYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMADDWDrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULDQYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULDQrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHRSWYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHRSWrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHUWYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHUWrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHWYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULHWrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULLWYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULLWrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULUDQYrr")>;
def: InstRW<[SKLWriteResGroup49], (instregex "VPMULUDQrr")>;
--
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 36828] New: [X86] SkylakeServer scheduler model doesn't account for port 0 and 1 being joined for 512 bit operations
https://bugs.llvm.org/show_bug.cgi?id=36828 Bug ID: 36828 Summary: [X86] SkylakeServer scheduler model doesn't account for port 0 and 1 being joined for 512 bit operations Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: craig.top...@gmail.com CC: llvm-bugs@lists.llvm.org I'm not sure how to model this in the scheduler, but 512 bit ALU instructions need to go out on port 0 and 1 simultaneously or on port 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] Issue 7040 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in AnalyzeImplicitConversions
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-03-21 Type: Bug New issue 7040 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in AnalyzeImplicitConversions https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7040 Detailed report: https://oss-fuzz.com/testcase?key=6274203666874368 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fffefa27bb8 Crash State: AnalyzeImplicitConversions Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802211531:201802220624 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6274203666874368 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] Issue 7041 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
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-03-21 Type: Bug New issue 7041 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7041 Detailed report: https://oss-fuzz.com/testcase?key=5003149141082112 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdf45c5bd8 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802020657:201802030042 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5003149141082112 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] Issue 7042 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
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-03-21 Type: Bug New issue 7042 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7042 Detailed report: https://oss-fuzz.com/testcase?key=5662538046898176 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff3b019a78 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5662538046898176 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] Issue 7044 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseName
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-03-21 Type: Bug New issue 7044 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Stack-overflow in Db::parseName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7044 Detailed report: https://oss-fuzz.com/testcase?key=5128361153134592 Project: llvm Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer Fuzz target binary: llvm-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fffc1a40ff8 Crash State: Db::parseName Db::parseEncoding Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803190520:201803200524 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5128361153134592 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
