[llvm-bugs] Issue 4601 in oss-fuzz: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Comment #4 on issue 4601 by ClusterFuzz-External: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4601#c4 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=5315067781316608 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd79025de8 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5315067781316608 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 4945 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: llvm::all_of(Mask, [&](int M) { return M < (NElts * 2) && M >= -1; }) && "Index
Comment #2 on issue 4945 by ClusterFuzz-External:
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: llvm::all_of(Mask, [&](int M) {
return M < (NElts * 2) && M >= -1; }) && "Index
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4945#c2
ClusterFuzz has detected this issue as fixed in range
201801030610:201801040618.
Detailed report: https://oss-fuzz.com/testcase?key=5354413934772224
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2
Fuzz target binary: llvm-isel-fuzzer--x86_64-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: ASSERT
Crash Address:
Crash State:
llvm::all_of(Mask, [&](int M) { return M < (NElts * 2) && M >= -1; })
&& "Index
llvm::SelectionDAG::getVectorShuffle
llvm::X86TargetLowering::LowerEXTRACT_VECTOR_ELT
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5354413934772224
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 4843 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!"
Comment #2 on issue 4843 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4843#c2 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=6533646933557248 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Num < NumOperands && "Invalid child # of SDNode!" DAGCombiner::visit DAGCombiner::combine Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6533646933557248 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 4910 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Idx < getValueType(0).getVectorNumElements() && "Idx out of range!"
Comment #2 on issue 4910 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Idx < getValueType(0).getVectorNumElements() && "Idx out of range!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4910#c2 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=5763109399560192 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: Idx < getValueType(0).getVectorNumElements() && "Idx out of range!" llvm::ShuffleVectorSDNode::getMaskElt DAGCombiner::visit Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5763109399560192 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 4630 in oss-fuzz: llvm: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
Comment #3 on issue 4630 by ClusterFuzz-External: llvm: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4630#c3 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=5320234895409152 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe3257c8e8 Crash State: llvm::detail::IEEEFloat::convertFromStringSpecials llvm::detail::IEEEFloat::convertFromString clang::NumericLiteralParser::GetFloatValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711160610:201712080609 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5320234895409152 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 4265 in oss-fuzz: llvm: Stack-overflow in GetDeclSpecTypeForDeclarator
Comment #4 on issue 4265 by ClusterFuzz-External: llvm: Stack-overflow in GetDeclSpecTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4265#c4 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=4610100405731328 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc28c2ce58 Crash State: GetDeclSpecTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4610100405731328 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 4803 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!"
Comment #2 on issue 4803 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4803#c2 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=5800967120355328 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" llvm::DAGTypeLegalizer::SplitVecOp_EXTRACT_VECTOR_ELT llvm::DAGTypeLegalizer::SplitVectorOperand Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5800967120355328 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 4265 in oss-fuzz: llvm: Stack-overflow in GetDeclSpecTypeForDeclarator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 4265 by ClusterFuzz-External: llvm: Stack-overflow in GetDeclSpecTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4265#c5 ClusterFuzz testcase 4610100405731328 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 4601 in oss-fuzz: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 4601 by ClusterFuzz-External: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4601#c5 ClusterFuzz testcase 5315067781316608 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 4871 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t"
Comment #3 on issue 4871 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4871#c3 ClusterFuzz has detected this issue as fixed in range 201801030610:201801040618. Detailed report: https://oss-fuzz.com/testcase?key=5497937917378560 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: getActiveBits() <= 64 && "Too many bits for uint64_t" canEvaluateShifted llvm::InstCombiner::FoldShiftByConstant Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5497937917378560 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 4945 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: llvm::all_of(Mask, [&](int M) { return M < (NElts * 2) && M >= -1; }) && "Index
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 4945 by ClusterFuzz-External:
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: llvm::all_of(Mask, [&](int M) {
return M < (NElts * 2) && M >= -1; }) && "Index
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4945#c3
ClusterFuzz testcase 5354413934772224 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 4630 in oss-fuzz: llvm: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4630 by ClusterFuzz-External: llvm: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4630#c4 ClusterFuzz testcase 5320234895409152 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 4871 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4871 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4871#c4 ClusterFuzz testcase 5497937917378560 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 4803 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 4803 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4803#c3 ClusterFuzz testcase 5800967120355328 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 4910 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Idx < getValueType(0).getVectorNumElements() && "Idx out of range!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 4910 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Idx < getValueType(0).getVectorNumElements() && "Idx out of range!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4910#c3 ClusterFuzz testcase 5763109399560192 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 4843 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 4843 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4843#c3 ClusterFuzz testcase 6533646933557248 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 35818] New: Crash when compiling coroutine with custom suspend_always
https://bugs.llvm.org/show_bug.cgi?id=35818 Bug ID: 35818 Summary: Crash when compiling coroutine with custom suspend_always Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: zaug...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19623 --> https://bugs.llvm.org/attachment.cgi?id=19623&action=edit The original source Compiling the attached codes leads to a crash, but when the custom suspend_always is replaced by std::experimental::suspend_always it works. -- 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 35819] New: lld overwrites first byte of jump table
https://bugs.llvm.org/show_bug.cgi?id=35819
Bug ID: 35819
Summary: lld overwrites first byte of jump table
Product: lld
Version: unspecified
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: enhancement
Priority: P
Component: MachO
Assignee: unassignedb...@nondot.org
Reporter: t.sch...@gmx.de
CC: llvm-bugs@lists.llvm.org
lld seems to overwrite the first byte of the jump table. Consider the following
program
inline int some_number()
{
return 0;
}
int main()
{
switch (some_number())
{
case 0:
break;
case 1:
break;
case 2:
break;
case 3:
break;
}
}
Compiling this results in
% clang++ -v
Apple LLVM version 8.1.0 (clang-802.0.42)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir:
/Applications/Xcode8.3.3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
% clang++ -c -o main.cpp.o main.cpp
% otool -tV main.cpp.o
build/main.cpp.o:
(__TEXT,__text) section
_main:
pushq %rbp
...
0059 nopl _main(%rax)
005c .long 4294967264 @ KIND_JUMP_TABLE32
0060 .long 4294967269 @ KIND_JUMP_TABLE32
0064 .long 4294967274 @ KIND_JUMP_TABLE32
0068 .long 4294967279 @ KIND_JUMP_TABLE32
006c nopl (%rax)
When linking this program with ld I get
% ld -v
@(#)PROGRAM:ld PROJECT:ld64-278.4
configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h
armv6m armv7k armv7m armv7em (tvOS)
LTO support using: LLVM version 8.1.0, (clang-802.0.42)
TAPI support using: Apple TAPI version 1.33.11
% ld -arch x86_64 -o main-ld main.cpp.o -lSystem
% otool -t main-ld
main-ld:
Contents of (__TEXT,__text) section
00010f20 55 48 89 e5 48 83 ec 20 c7 45 fc 00 00 00 00 e8
00010f30 64 00 00 00 89 c1 89 ca 83 e8 03 48 89 55 f0 89
00010f40 45 ec 0f 87 28 00 00 00 48 8d 05 2d 00 00 00 48
00010f50 8b 4d f0 48 63 14 88 48 01 c2 ff e2 e9 0f 00 00
00010f60 00 e9 0a 00 00 00 e9 05 00 00 00 e9 00 00 00 00
00010f70 8b 45 fc 48 83 c4 20 5d c3 0f 1f 00 e0 ff ff ff
00010f80 e5 ff ff ff ea ff ff ff ef ff ff ff 0f 1f 40 00
00010f90 55 48 89 e5 31 c0 5d c3
The first jump table entry is at 0x10f20 + 0x5c = 0x10F7C and has the
value ffe0 (or 4294967264 in decimal) which is the value from the object
file.
Now, doing the same with lld I get
% ~/foreign/llvm-master-install/bin/ld64.lld -arch x86_64 -o main-lld
main.cpp.o -lSystem
% otool -t main-lld
main-lld:
Contents of (__TEXT,__text) section
00010f30 55 48 89 e5 48 83 ec 20 c7 45 fc 00 00 00 00 e8
00010f40 5c 00 00 00 89 c1 89 ca 83 e8 03 48 89 55 f0 89
00010f50 45 ec 0f 87 28 00 00 00 48 8d 05 2d 00 00 00 48
00010f60 8b 4d f0 48 63 14 88 48 01 c2 ff e2 e9 0f 00 00
00010f70 00 e9 0a 00 00 00 e9 05 00 00 00 e9 00 00 00 00
00010f80 8b 45 fc 48 83 c4 20 5d c3 0f 1f 00 a4 ff ff ff
00010f90 e5 ff ff ff ea ff ff ff ef ff ff ff 90 ff ff ff
00010fa0 55 48 89 e5 31 c0 5d c3
The first jump table entry is at 0x10f30 + 0x5c = 0x10F8C and has the
value ffa4 (or 4294967204 in decimal) which is NOT the value from the
object file. In particular, the first byte is a4 instead of e0. I'm not sure if
that's a coincidence, but this jumps to the start of the function (and not to
the appropriate case handler).
Note that lld was built from LLVM commit
f494e856dbbecfdc2958a07cd4acc3c6a7ed7533 and lld commit
874cf0193393de7ad4b480d8519a6e40375cf938. Also I only tried this for MachO.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35820] New: LLVM 6 fails to compile pocl's shuffle test
https://bugs.llvm.org/show_bug.cgi?id=35820 Bug ID: 35820 Summary: LLVM 6 fails to compile pocl's shuffle test Product: new-bugs Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: ra...@runbox.com CC: llvm-bugs@lists.llvm.org Created attachment 19626 --> https://bugs.llvm.org/attachment.cgi?id=19626&action=edit simplified test case I've attached a simplified test case. When trying to compile it with "llc -O2", LLVM 5's llc is successful but LLVM 6 fails with: llc: /home/0/LLVM_git/60/lib/Target/X86/X86ISelLowering.cpp:5775: bool getTargetShuffleMask(llvm::SDNode*, llvm::MVT, bool, llvm::SmallVectorImpl&, llvm::SmallVectorImpl&, bool&): Assertion `N->getOperand(1).getValueType() == VT && "Unexpected value type"' failed. Clang+LLVM compiled today (4th Jan 2018) from freshly updated git: clang version 6.0.0 (http://llvm.org/git/clang.git db28ee2ff44111ade7c6e1078ef80910978b6b94) machine: AMD 1700X, gcc 7.2.1 -- 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 4954 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (RetVT == MVT::i8 || RetVT == MVT::i16 || RetVT == MVT::i32 || RetVT == MVT::i64
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-04 Type: Bug New issue 4954 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (RetVT == MVT::i8 || RetVT == MVT::i16 || RetVT == MVT::i32 || RetVT == MVT::i64 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4954 Detailed report: https://oss-fuzz.com/testcase?key=4920292062265344 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (RetVT == MVT::i8 || RetVT == MVT::i16 || RetVT == MVT::i32 || RetVT == MVT::i64 AArch64FastISel::emitASR_ri AArch64FastISel::fastSelectInstruction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801020611:201801030610 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4920292062265344 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 22965] [x86] Less optimized multi-byte nop instructions are generated
https://bugs.llvm.org/show_bug.cgi?id=22965 Simon Pilgrim changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED CC||craig.top...@gmail.com --- Comment #4 from Simon Pilgrim --- Reopening - this isn't really a duplicate, but should be implemented with the changes that will be done for Bug #31225. -- 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 3640 in oss-fuzz: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer
Updates: Labels: Deadline-Approaching Comment #5 on issue 3640 by sheriff...@chromium.org: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3640#c5 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3638 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type
Updates: Labels: Deadline-Approaching Comment #5 on issue 3638 by sheriff...@chromium.org: llvm/llvm-demangle-fuzzer: Stack-overflow in char const* parse_type https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3638#c5 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 35794] [InstCombine] Assertion due to mismatch of integer and pointer types
https://bugs.llvm.org/show_bug.cgi?id=35794 Sanjay Patel changed: What|Removed |Added Fixed By Commit(s)||321801 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sanjay Patel --- https://reviews.llvm.org/rL321801 -- 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 35821] New: Invalid shift amount assertion in -aa-eval
https://bugs.llvm.org/show_bug.cgi?id=35821
Bug ID: 35821
Summary: Invalid shift amount assertion in -aa-eval
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Global Analyses
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: alina.sbir...@gmail.com, llvm-bugs@lists.llvm.org,
nunoplo...@sapo.pt, spatel+l...@rotateright.com,
yyc1...@gmail.com
Reduced from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4708
opt -aa-eval
define void @f() {
%G26 = getelementptr i1, i1* undef, i1 undef
%B20 = shl i8 -128, 16
%G47 = getelementptr i1*, i1** undef, i8 %B20
unreachable
}
Assertion failed: ShiftAmt <= BitWidth && "Invalid shift amount", file
D:\LLVM\llvm\include\llvm/ADT/APInt.h, line 894
--
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 35822] New: [AArch64] Detected cycle in SelectionDAG
https://bugs.llvm.org/show_bug.cgi?id=35822
Bug ID: 35822
Summary: [AArch64] Detected cycle in SelectionDAG
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: AArch64
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: florian.h...@arm.com, llvm-bugs@lists.llvm.org,
sam.par...@arm.com, tim.northo...@arm.com
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4856
llc -mtriple=aarch64-unknown
define void @foo(<4 x i32>* %A, <4 x i32>* %B, <4 x i32>* %C, <4 x i32>* %D, <4
x i32>* %E, <4 x i32>* %F, <4 x i32>* %G, <4 x i32>* %H, <4 x i32>* %I, <4 x
i32>* %J, <4 x i32>* %K, <4 x i32>* %L, <4 x i32>* %M, <4 x i32>* %N, <4 x
i32>* %O, <4 x i32>* %P, <4 x i32>* %Q, <4 x i32>* %R, <4 x i32>* %S, <4 x
i32>* %T, <4 x i32>* %U, <4 x i32>* %V, <4 x i32>* %W, <4 x i32>* %X, <4 x
i32>* %Y, <4 x i32>* %Z, <4 x i32>* %BA, <4 x i32>* %BB, <4 x i32>* %BC, <4 x
i32>* %BD, <4 x i32>* %BE, <4 x i32>* %BF, <4 x i32>* %BG, <4 x i32>* %BH, <4 x
i32>* %BI, <4 x i32>* %BJ, <4 x i32>* %BK, <4 x i32>* %BL, <4 x i32>* %BM, <4 x
i32>* %BN, <4 x i32>* %BO, <4 x i32>* %BP, <4 x i32>* %BQ, <4 x i32>* %BR, <4 x
i32>* %BS, <4 x i32>* %BT, <4 x i32>* %BU, <4 x i32>* %BV, <4 x i32>* %BW, <4 x
i32>* %BX, <4 x i32>* %BY, <4 x i32>* %BZ, <4 x i32>* %CA, <4 x i32>* %CB, <4 x
i32>* %CC, <4 x i32>* %CD, <4 x i32>* %CE, <4 x i32>* %CF, <4 x i32>* %CG, <4 x
i32>* %CH, <4 x i32>* %CI, <4 x i32>* %CJ, <4 x i32>* %CK, <4 x i32>* %CL) {
%A5 = alloca i32
%L3 = load i32, i32* %A5
%L1 = load i64, i64* undef
%d = select <4 x i1> , <4 x i32>
zeroinitializer, <4 x i32>
%G2 = getelementptr i32, i32* %A5, i64 %L1
%L2 = load i32, i32* %G2
%j = select <4 x i1> , <4 x i32>
zeroinitializer, <4 x i32>
%bm = select <4 x i1> , <4 x i32> , <4 x i32>
%I4 = insertelement <4 x i32> %d, i32 %L3, i32 %L2
store <4 x i32> %d, <4 x i32>* %F
store <4 x i32> %d, <4 x i32>* %I
store <4 x i32> %j, <4 x i32>* %J
store <4 x i32> %d, <4 x i32>* %BI
store <4 x i32> %I4, <4 x i32>* %BW
store <4 x i32> %j, <4 x i32>* %CG
store <4 x i32> %j, <4 x i32>* %CJ
store <4 x i32> %bm, <4 x i32>* %CL
ret void
}
--
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 35823] New: Merge r321754 into 6.0.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35823 Bug ID: 35823 Summary: Merge r321754 into 6.0.0 branch Product: clang Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Modules Assignee: unassignedclangb...@nondot.org Reporter: apra...@apple.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org I'm nominating r321754 (-gmodules: Emit debug info for implicit module imports via #include) for the 6.0.0 branch. This is a bugfix that affects Clang modules and LLDB on platforms with -debugger-tuning=lldb and is NFC everywhere else. There is a regression test in LLDB that depends on 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 35826] New: LLVM 6 _Generic keyword with OpenCL produces false error
https://bugs.llvm.org/show_bug.cgi?id=35826 Bug ID: 35826 Summary: LLVM 6 _Generic keyword with OpenCL produces false error Product: new-bugs Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: ra...@runbox.com CC: llvm-bugs@lists.llvm.org Created attachment 19629 --> https://bugs.llvm.org/attachment.cgi?id=19629&action=edit reproducer Compiling the attached code sample with LLVM 5 works, but fails with LLVM 6. -- $ /bin/clang -x cl -cl-kernel-arg-info -cl-std=CL1.2 -o /tmp/test2.o -c test1.cl -include /lib/clang/5.0.1/include/opencl-c.h ... no error -- $ /bin/clang -x cl -cl-kernel-arg-info -cl-std=CL1.2 -o /tmp/test2.o -c test1.cl -include /lib/clang/6.0.0/include/opencl-c.h test1.cl:13:18: error: controlling expression type 'stype' (aka 'float') not compatible with any generic association type _Static_assert ( is_floating(stype), "stype"); ^~ test1.cl:3:35: note: expanded from macro 'is_floating' # define is_floating(T) _Generic((T)(0.0f), float: 1, double: 1) ^ 1 error generated. - I understand _Generic is a C11 keyword, but Clang documentation states: As an extension, the C11 generic selection expression is available in all languages supported by Clang. The syntax is the same as that given in the C11 standard. has this changed ? -- 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 4707 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Use-after-poison in DAGCombiner::useDivRem
Comment #2 on issue 4707 by amara.em...@gmail.com: llvm/llvm-isel-fuzzer--x86_64-O2: Use-after-poison in DAGCombiner::useDivRem https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4707#c2 Should be fixed in r321813. -- 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 35827] New: Clang crashes with computed goto
https://bugs.llvm.org/show_bug.cgi?id=35827 Bug ID: 35827 Summary: Clang crashes with computed goto Product: clang Version: 5.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: i...@ct800.net CC: llvm-bugs@lists.llvm.org Created attachment 19630 --> https://bugs.llvm.org/attachment.cgi?id=19630&action=edit Preprocessed sources and run script I'm using Win7-x64 and Android NDK 16b. I have generated the standalone chain for Android Arm64 that uses Clang 5.0.300080 to generate 64 bit code. When compiling a C file that contains a shellsort using computed goto jump tables, Clang crashes. The error message suggest to file a bug report. When I replaced the computed goto shellsort with a version that does not use computed goto, Clang did not crash and produced a binary, as intended. So it has something to do with the computed goto. I tried to isolate this computed goto shellsort into a single file and just sorting integers, but that did not crash Clang. So the issue is more complex than just computed goto. I'm also using the Android NDK 16b standalone toolchain configured for Armv7-a with 32 bit target with the same application and the computed goto shellsort, and this works without problems. -- 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 35828] New: lld ignores /usr/lib/rcrt1.o crt file
https://bugs.llvm.org/show_bug.cgi?id=35828
Bug ID: 35828
Summary: lld ignores /usr/lib/rcrt1.o crt file
Product: lld
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedb...@nondot.org
Reporter: bjornpa...@gmail.com
CC: llvm-bugs@lists.llvm.org
In musl-1.1.10 and foward, musl provides rcrt1 in addition to crt{1,i,n}. This
new crt start file, rcrt1.o, is provided for producing static-linked position
independent executables (PIE). [1]
rcrt1.o is a dependency of musl, and musl will not compile unless it is able to
access the __dls2 function that is defined in it.
GNU linkers such as bfd and gold have added support for including this file,
and musl compiles with no issue. But when I tried to use lld as a drop in
replacement, the build fails, and the lld throws this error:
/usr/bin/x86_64-gentoo-linux-musl-ld: error: undefined symbol: __dls2
>>> referenced by ld-temp.o
>>> lto.tmp:(_dlstart_c)
clang-5.0: error: linker command failed with exit code 1 (use -v to see
invocation)
A couple grep -R's in lld's source code didn't reveal anything concerning
rcrt1, so I am assuming it has not been implemented yet.
lld version is 5.0.1
[1] https://www.musl-libc.org/oldversions.html
--
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 35222] Regression from r313116: gvn-hoist incorrectly erases load
https://bugs.llvm.org/show_bug.cgi?id=35222 Eli Friedman changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Eli Friedman --- https://reviews.llvm.org/D41453 -- 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 35830] New: Merge r321789 into 6.0.0 branch: [GVNHoist] Fix: PR35222 gvn-hoist incorrectly erases load in case of a loop
https://bugs.llvm.org/show_bug.cgi?id=35830 Bug ID: 35830 Summary: Merge r321789 into 6.0.0 branch: [GVNHoist] Fix: PR35222 gvn-hoist incorrectly erases load in case of a loop Product: libraries Version: 6.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: efrie...@codeaurora.org CC: h...@chromium.org, hiradi...@msn.com, llvm-bugs@lists.llvm.org, sebpop.l...@gmail.com Blocks: 35804 Straightforward bugfix. Very low risk, since GVNHoist isn't part of the default pass pipeline. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35831] New: After r315899, labels after x86 prefixes cause errors
https://bugs.llvm.org/show_bug.cgi?id=35831 Bug ID: 35831 Summary: After r315899, labels after x86 prefixes cause errors Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dimi...@andric.com CC: llvm-bugs@lists.llvm.org Related to bug 35741, after https://reviews.llvm.org/rL315899 (fixing x86 prefix issues related to bug 7709, bug 17697, bug 19251, bug 32809 and bug 21640), labels directives directly after an x86 instruction prefix are no longer accepted. For example (this is derived from openjdk8 sources, see [1]): cmp $0, %edx je 1f lock 1: cmpxchgl %ecx,(%rdi) This is accepted by both clang before r315899 and GNU as, but clang r315899 gives: lock-label.s:4:2: error: unknown token in expression 1: cmpxchgl %ecx,(%rdi) ^ lock-label.s:2:5: error: directional label undefined je 1f ^ [1] http://hg.openjdk.java.net/jdk8/jdk8/hotspot/file/87ee5ee27509/src/os_cpu/linux_x86/vm/atomic_linux_x86.inline.hpp#l48 -- 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 35832] New: ambiguity accessing anonymous union member present in multiple bases despite explicit qualification
https://bugs.llvm.org/show_bug.cgi?id=35832
Bug ID: 35832
Summary: ambiguity accessing anonymous union member present in
multiple bases despite explicit qualification
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: rjmcc...@apple.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
harza:/tmp$ cat red.cpp
class B {
protected:
int i;
union { int j; };
};
class X : public B { };
class Y : public B { };
class Z : public X, public Y {
int a() { return X::i; } // works
int b() { return X::j; } // fails
};
harza:/tmp$ clang red.cpp
red.cpp:12:22: error: ambiguous conversion from derived class 'Z' to base class
'B':
class Z -> class X -> class B
class Z -> class Y -> class B
int b() { return X::j; } // fails
^
1 error generated.
Report by Dave Zarzycki!
--
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 35833] New: [PCG] Failed to merge identical lower/upper 128-bit shuffles into 256-bit shuffle
https://bugs.llvm.org/show_bug.cgi?id=35833
Bug ID: 35833
Summary: [PCG] Failed to merge identical lower/upper 128-bit
shuffles into 256-bit shuffle
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: konstantin.belocha...@sony.com
CC: llvm-bugs@lists.llvm.org
__m256 shuf0(__m256 a, __m256 b)
{
return
__builtin_shufflevector(a, b, 0, 2, 4, 6, 8, 10, 12, 14);
}
_Z5shuf0Dv8_fS_:
vextractf128 xmm2,ymm1,1
vshufps xmm1,xmm1,xmm2,88h
vextractf128 xmm2,ymm0,1
vshufps xmm0,xmm0,xmm2,88h
vinsertf128 ymm0,ymm0,xmm1,1
ret
__m256 shuf1(__m256 a, __m256 b)
{
return
__builtin_shufflevector(a, b, 1, 3, 5, 7, 9, 11, 13, 15);
}
_Z5shuf1Dv8_fS_:
vextractf128 xmm2,ymm1,1
vshufps xmm1,xmm1,xmm2,0DDh
vextractf128 xmm2,ymm0,1
vshufps xmm0,xmm0,xmm2,0DDh
vinsertf128 ymm0,ymm0,xmm1,1
ret
Which means that this is far more complicated than it needs to be
__m256 add_shuf0_shuf1(__m256 a, __m256 b)
{
return
__builtin_shufflevector(a, b, 0, 2, 4, 6, 8, 10, 12, 14) +
__builtin_shufflevector(a, b, 1, 3, 5, 7, 9, 11, 13, 15);
}
_Z15add_shuf0_shuf1Dv8_fS_:
vextractf128 xmm2,ymm1,1
vshufps xmm3,xmm1,xmm2,88h
vextractf128 xmm4,ymm0,1
vshufps xmm5,xmm0,xmm4,88h
vinsertf128 ymm3,ymm5,xmm3,1
vshufps xmm1,xmm1,xmm2,0DDh
vshufps xmm0,xmm0,xmm4,0DDh
vinsertf128 ymm0,ymm0,xmm1,1
vaddps ymm0,ymm3,ymm0
ret
These 256-bit shuffles could be achieved as a VPERM2F128 followed by a VSHUFPS
--
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
