[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
Comment #4 on 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#c4 ClusterFuzz has detected this issue as fixed in range 201801230732:201801240651. 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 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801230732:201801240651 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4920292062265344 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 5227 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <
Comment #3 on issue 5227 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5227#c3 ClusterFuzz has detected this issue as fixed in range 201801230732:201801240651. Detailed report: https://oss-fuzz.com/testcase?key=6228718214184960 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: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & llvm::MachineIRBuilder::buildExtract llvm::LegalizerHelper::narrowScalar Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801020611:201801030610 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801230732:201801240651 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6228718214184960 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 4954 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (RetVT == MVT::i8 || RetVT == MVT::i16 || RetVT == MVT::i32 || RetVT == MVT::i64
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on 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#c5 ClusterFuzz testcase 4920292062265344 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 5227 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 5227 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5227#c4 ClusterFuzz testcase 6228718214184960 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 5647 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, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-24 Type: Bug New issue 5647 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=5647 Detailed report: https://oss-fuzz.com/testcase?key=4634333408133120 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::emitLSL_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=4634333408133120 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 36074] New: undefined behavior in SelectionDAGAddressAnalysis.cpp
https://bugs.llvm.org/show_bug.cgi?id=36074 Bug ID: 36074 Summary: undefined behavior in SelectionDAGAddressAnalysis.cpp Product: new-bugs Version: trunk Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: yannlaiglecha...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19738 --> https://bugs.llvm.org/attachment.cgi?id=19738&action=edit reduced code With the attached reduced file: > llc -O1 SelectionDAG_UB.ll [...]lib/CodeGen/SelectionDAG/SelectionDAGAddressAnalysis.cpp:23:22: runtime error: signed integer overflow: 7124803381091165632 - -7949118599238474896 cannot be represented in type 'long long' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior [...]lib/CodeGen/SelectionDAG/SelectionDAGAddressAnalysis.cpp:23:22 in Stack dump: 0. Program arguments: llc -O1 SelectionDAG_UB.ll 1. Running pass 'Function Pass Manager' on module 'SelectionDAG_UB.ll'. 2. Running pass 'X86 DAG->DAG Instruction Selection' on function '@Test' -- 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 35735] The default object format for wasm is ELF
https://bugs.llvm.org/show_bug.cgi?id=35735 Nicholas Wilson changed: What|Removed |Added CC||n...@realvnc.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nicholas Wilson --- This was fixed in rL323220 (https://reviews.llvm.org/rL323220) -- 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 5650 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: VRegInfo[Reg].first.is() && "Register class not set
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-24 Type: Bug New issue 5650 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: VRegInfo[Reg].first.isTargetRegisterClass *>() && "Register class not set https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5650 Detailed report: https://oss-fuzz.com/testcase?key=4830723824418816 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: VRegInfo[Reg].first.is() && "Register class not set llvm::MachineRegisterInfo::getRegClass llvm::InstructionSelect::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801230732:201801240651 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4830723824418816 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 32037] clang is slower than gcc when compiling some codes in chrome
https://bugs.llvm.org/show_bug.cgi?id=32037 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||323320 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #29 from Simon Pilgrim --- rL323320 - resolving this. There might be further micro-optimizations that can be made but the main bulk of it is done now. -- 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 24345] [Meta] ChromeOs+Clang platform support
https://bugs.llvm.org/show_bug.cgi?id=24345 Bug 24345 depends on bug 32037, which changed state. Bug 32037 Summary: clang is slower than gcc when compiling some codes in chrome https://bugs.llvm.org/show_bug.cgi?id=32037 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 34571] Missing mnemonic RDPID
https://bugs.llvm.org/show_bug.cgi?id=34571 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||316332 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Pilgrim --- asm/disasm support was added at rL316332 - so it missed 4.0/5.0 but is included in the 6.0 release. Note: The intrinsics support was completed at rL323047 so missed the 6.0 release branch, but this bug was about the mnemonic. -- 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 36075] New: break in statement expression results in -Wunreachable-code
https://bugs.llvm.org/show_bug.cgi?id=36075
Bug ID: 36075
Summary: break in statement expression results in
-Wunreachable-code
Product: clang
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: wielkie...@gmail.com
CC: llvm-bugs@lists.llvm.org
The following code results in -Wunreachable-code on clang 5.0 and trunk:
int main()
{
while (true)
{
({ break; });
}
}
prog.cc:5:9: warning: code will never be executed [-Wunreachable-code]
({ break; });
^~~~
It seems the trigger is an unconditional "break" statement as the last one of
the expression statement.
The warning goes away after putting the expression statement inside a macro
which might be related to a fix for bug 13747, but the warning shouldn't be
generated regardless.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36070, which changed state. Bug 36070 Summary: [lld] Merge r323221 into the 6.0 branch https://bugs.llvm.org/show_bug.cgi?id=36070 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 36070] [lld] Merge r323221 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=36070 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Hans Wennborg --- Merged in r323327. -- 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 32672] (Visual Studio) Unknown arguments misrecognized as input files
https://bugs.llvm.org/show_bug.cgi?id=32672 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #6 from Hans Wennborg --- (In reply to Reupen Shah from comment #5) > /permissive- is now the default for new projects in Visual Studio 2017, so > this is quite a big problem for that specific flag. > > I verified that this bug still applies for /permissive- as of LLVM revision > 322435. It's easy to teach clang-cl (and I assume lld too) to parse unknown flags. I've added /permissive- and the /Bt flags to clang-cl in r323330. Please let me know if there are more. -- 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 36045] clang crashes on valid code at -O3 on x86_64-linux-gnu while running pass 'Simplify the CFG'
https://bugs.llvm.org/show_bug.cgi?id=36045 Sanjay Patel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Sanjay Patel --- https://reviews.llvm.org/rL323331 Unfortunately, this pushes the underlying problems for other passes (jump-threading, simplifycfg, correlated-propagation) into hiding. If someone wants to uncover those again, the first draft of this patch at D42442 would do that (it would assert rather than bail out). Resolving as "fixed" because we won't crash anymore, but there are potentially better fixes as discussed here. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36043, which changed state. Bug 36043 Summary: Merge clang r323008 into 6.0 branch: [Lex] Fix crash on code completion in comment in included file. https://bugs.llvm.org/show_bug.cgi?id=36043 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 36043] Merge clang r323008 into 6.0 branch: [Lex] Fix crash on code completion in comment in included file.
https://bugs.llvm.org/show_bug.cgi?id=36043 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- Merged in r32 -- 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 35840] clang crashes on valid code at -O2 and -O3 while running pass 'Jump Threading'
https://bugs.llvm.org/show_bug.cgi?id=35840 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Sanjay Patel --- https://reviews.llvm.org/rL323331 Unfortunately, this pushes the underlying problems for other passes (jump-threading, simplifycfg, correlated-propagation) into hiding. If someone wants to uncover those again, the first draft of this patch at D42442 would do that (it would assert rather than bail out). Resolving as "fixed" because we won't crash anymore, but there are potentially better fixes as discussed here. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35812] PowerPC: cmpxchg generates incorrect code for i16 and i8
https://bugs.llvm.org/show_bug.cgi?id=35812 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #7 from Hans Wennborg --- Merged in r323334. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 35812, which changed state. Bug 35812 Summary: PowerPC: cmpxchg generates incorrect code for i16 and i8 https://bugs.llvm.org/show_bug.cgi?id=35812 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36057, which changed state. Bug 36057 Summary: [X86][SSE] Merge r323190 into 6.00 branch https://bugs.llvm.org/show_bug.cgi?id=36057 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 36057] [X86][SSE] Merge r323190 into 6.00 branch
https://bugs.llvm.org/show_bug.cgi?id=36057 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- Merged in r323335. -- 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 36045] clang crashes on valid code at -O3 on x86_64-linux-gnu while running pass 'Simplify the CFG'
https://bugs.llvm.org/show_bug.cgi?id=36045 Sanjay Patel changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #10 from Sanjay Patel --- Reopening pending a decision to make the fix in the release. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36045, which changed state. Bug 36045 Summary: clang crashes on valid code at -O3 on x86_64-linux-gnu while running pass 'Simplify the CFG' https://bugs.llvm.org/show_bug.cgi?id=36045 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36071, which changed state. Bug 36071 Summary: Please port r322359, r322421 and r322801 to 6.0 https://bugs.llvm.org/show_bug.cgi?id=36071 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 36071] Please port r322359, r322421 and r322801 to 6.0
https://bugs.llvm.org/show_bug.cgi?id=36071 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Hans Wennborg --- Merged in r323336. -- 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 36076] New: Stores to union incorrectly reordered
https://bugs.llvm.org/show_bug.cgi?id=36076
Bug ID: 36076
Summary: Stores to union incorrectly reordered
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: momchil.veli...@arm.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19739
--> https://bugs.llvm.org/attachment.cgi?id=19739&action=edit
minimal testcase
The attached test program is mis-compiled at all optimisation levels, except
-O0, for X86_64, Arm and likely for all targets.
./bin/clang -target x86_64-linux -O2 union-store.c
$ ./a.out
value = 3, should be 2
This happens in Dead Store Elimination:
*** IR Dump After Value Propagation ***
; Function Attrs: norecurse nounwind
define void @f() local_unnamed_addr #0 {
entry:
store i32 5, i32* getelementptr inbounds (%union.U, %union.U* @a, i32 0, i32
0), align 4, !tbaa !3
%0 = load i16*, i16** bitcast (%union.U** @b to i16**), align 4, !tbaa !6
store i16 3, i16* %0, align 4, !tbaa !3
store i16 2, i16* bitcast (%union.U* @a to i16*), align 4, !tbaa !3
ret void
}
*** IR Dump After Dead Store Elimination ***
; Function Attrs: norecurse nounwind
define void @f() local_unnamed_addr #0 {
entry:
store i32 2, i32* getelementptr inbounds (%union.U, %union.U* @a, i32 0, i32
0), align 4, !tbaa !3
%0 = load i16*, i16** bitcast (%union.U** @b to i16**), align 4, !tbaa !6
store i16 3, i16* %0, align 4, !tbaa !3
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 36077] New: Single-(non-list) element braced initializer argument rejects user defined conversion
https://bugs.llvm.org/show_bug.cgi?id=36077
Bug ID: 36077
Summary: Single-(non-list) element braced initializer argument
rejects user defined conversion
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: hst...@ca.ibm.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
In the following, the copy list-initialization of the parameter of foo, which
is of non-aggregate class type, from the single-(non-list) element
braced-init-list should succeed through selection of A's copy constructor in
the second phase of [over.match.list]. GCC compiles this code, as does MSVC and
ICC.
This appears to be related to CWG 2076, the resolution of which is included in
C++17.
### SOURCE ():
struct A { A(const A &); };
struct B { operator A() const; };
void foo(A);
void bar(const B &b) { foo({b}); }
### COMPILER INVOCATION COMMAND:
clang -cc1 -x c++ -std=c++17 -
### ACTUAL OUTPUT:
:5:24: error: no matching function for call to 'foo'
void bar(const B &b) { foo({b}); }
^~~
:4:6: note: candidate function not viable: cannot convert initializer
list argument to 'A'
void foo(A);
^
1 error generated.
### EXPECTED OUTPUT:
(Clean compile).
### COMPILER VERSION INFO (clang -v):
clang version 7.0.0 (https://github.com/llvm-mirror/clang.git
39491d7b6098f96eb1f88d68068eb654c1e2bd81)
(https://github.com/llvm-mirror/llvm.git
c127e0c9742f746fe7198222bf6442b81787292e)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/wandbox/clang-head/bin
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Selected multilib: .;@m64
--
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 36078] New: __attribute__((naked)) function loses parameter
https://bugs.llvm.org/show_bug.cgi?id=36078
Bug ID: 36078
Summary: __attribute__((naked)) function loses parameter
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Interprocedural Optimizations
Assignee: unassignedb...@nondot.org
Reporter: momchil.veli...@arm.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19740
--> https://bugs.llvm.org/attachment.cgi?id=19740&action=edit
minimal testcase
LLVM discards a parameter of a function, declared with the "naked" attribute.
Compiling the attached test program for Arm with `clang -target arm-eabi -O3 -S
naked.c` output the following assembly for `bar`:
bar:
.fnstart
b foo
i.e. the parameter to `foo` is not passed at all.
This change occurs during "Deduce function attributes", which marks the
parameter with "readnone" and subsequently it's removed by "Promote 'by
reference' arguments to scalars" pass.
*** IR Dump After Function Integration/Inlining ***
; Function Attrs: naked noinline nounwind
define internal fastcc i32 @foo(i32*) unnamed_addr #1 {
entry:
call void asm sideeffect "ldr r0, [r0] \0Abx lr\0A", ""() #2,
!srcloc !3
unreachable
}
*** IR Dump After Deduce function attributes ***
; Function Attrs: naked noinline nounwind
define internal fastcc i32 @foo(i32* nocapture readnone) unnamed_addr #1 {
entry:
call void asm sideeffect "ldr r0, [r0] \0Abx lr\0A", ""() #2,
!srcloc !3
unreachable
}
*** IR Dump After Promote 'by reference' arguments to scalars ***
; Function Attrs: naked noinline nounwind
define internal fastcc i32 @foo() unnamed_addr #1 {
entry:
call void asm sideeffect "ldr r0, [r0] \0Abx lr\0A", ""() #2,
!srcloc !3
unreachable
}
--
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 36079] New: Miscompilation in code which LLVM partially vectorizes
https://bugs.llvm.org/show_bug.cgi?id=36079 Bug ID: 36079 Summary: Miscompilation in code which LLVM partially vectorizes Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Backend: ARM Assignee: unassignedb...@nondot.org Reporter: momchil.veli...@arm.com CC: llvm-bugs@lists.llvm.org Created attachment 19741 --> https://bugs.llvm.org/attachment.cgi?id=19741&action=edit minimal testcase The attached test program is miscompiled by LLVM, when targeting Arm architecture, which includes NEON instructions, at optimisation levels -02, -O3, -Os and -Oz. All the elements of the array `c` are expected to be set to 1, however the last one (`c[3]`) stays 3. -- 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 36080] New: LLVM miscompiles variadic functions with overaligned stack when targeting Thumb1
https://bugs.llvm.org/show_bug.cgi?id=36080
Bug ID: 36080
Summary: LLVM miscompiles variadic functions with overaligned
stack when targeting Thumb1
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: ARM
Assignee: unassignedb...@nondot.org
Reporter: momchil.veli...@arm.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19742
--> https://bugs.llvm.org/attachment.cgi?id=19742&action=edit
minimal testcase
When compiling for Arm architecture, which implements only the 16-bit Thumb
instruction set (like Armv4t or Armv6m) a variadic function, which has
increased stack alignment requirements (so it dynamically re-aligns the SP),
the Arm back end generates invalid code to store the incoming variadic
arguments, which are passed in registers.
When the attached test case is compiled via
clang -target thumbv6m-eabi -O2 -S variadic-stack-align.c
the generated assembly looks like:
test:
.fnstart
.pad#12
sub sp, #12; allocate space for variadic register args
.save {r4, r6, r7, lr}
push{r4, r6, r7, lr}
.setfp r7, sp, #8
add r7, sp, #8
.pad#36
sub sp, #36 ;
mov r4, sp ;
lsrsr4, r4, #5 ; Align stack pointer
lslsr4, r4, #5 ;
mov sp, r4 ;
str r3, [sp, #60] ;
str r2, [sp, #56] ; Store incoming arguments
str r1, [sp, #52] ;
...
The offsets, used to store the register varargs are not correct after the SP is
aligned. Instead, the function should store these arguments via the FP.
--
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 36081] New: Merge r323360 into the 6.0 branch : [Hexagon] Accept lowercase b in -hvx-length=64b and -hvx-length=128b
https://bugs.llvm.org/show_bug.cgi?id=36081 Bug ID: 36081 Summary: Merge r323360 into the 6.0 branch : [Hexagon] Accept lowercase b in -hvx-length=64b and -hvx-length=128b Product: new-bugs Version: 6.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: kparz...@codeaurora.org CC: llvm-bugs@lists.llvm.org Blocks: 35804 Is it OK to merge the following revision(s) to the 6.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36044] Assert: "GlobalValue with DLLImport Storage is dso_local!
https://bugs.llvm.org/show_bug.cgi?id=36044 Rafael Ávila de Espíndola changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Rafael Ávila de Espíndola --- r323361. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36018, which changed state. Bug 36018 Summary: [GlobalISel][AArch64] Two load instructions generated for single volatile load https://bugs.llvm.org/show_bug.cgi?id=36018 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 36018] [GlobalISel][AArch64] Two load instructions generated for single volatile load
https://bugs.llvm.org/show_bug.cgi?id=36018 Amara Emerson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Amara Emerson --- Committed a workaround until we fix the issue properly with a G_SEXTLOAD in r323371. -- 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 36018] [GlobalISel][AArch64] Two load instructions generated for single volatile load
https://bugs.llvm.org/show_bug.cgi?id=36018 Eli Friedman changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #8 from Eli Friedman --- Needs to be cherry-picked to 6.0. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36018, which changed state. Bug 36018 Summary: [GlobalISel][AArch64] Two load instructions generated for single volatile load https://bugs.llvm.org/show_bug.cgi?id=36018 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 20855] tuple with a reference to a temporary (C++11): static_assert: "Attempted to construct a reference element in a tuple with an rvalue"
https://bugs.llvm.org/show_bug.cgi?id=20855 Eric Fiselier changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #16 from Eric Fiselier --- Fixed in r323380. The fallback check which generated false-positives has been removed and replaced to use the new Clang trait __reference_binds_to_temporary. -- 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 36082] New: Merge r322016 into the 6.0 branch
https://bugs.llvm.org/show_bug.cgi?id=36082 Bug ID: 36082 Summary: Merge r322016 into the 6.0 branch Product: new-bugs Version: 6.0 Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dimi...@andric.com CC: llvm-bugs@lists.llvm.org Please merge https://reviews.llvm.org/rL322016 into the 6.0 branch. This fixes a regression reported in bug 35717. -- 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 35564] include/c++/v1/list:507: _LIBCPP_ASSERT '__get_const_db()->__decrementable(this)' failed.
https://bugs.llvm.org/show_bug.cgi?id=35564 Eric Fiselier changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Eric Fiselier --- This should be fixed in r323390. -- 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 36083] New: Crash when multiple ATs map to the same AT>
https://bugs.llvm.org/show_bug.cgi?id=36083 Bug ID: 36083 Summary: Crash when multiple ATs map to the same AT> Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: rafael.espind...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19745 --> https://bugs.llvm.org/attachment.cgi?id=19745&action=edit testcase The attached testcase crashes. -- 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 36084] New: [X86] IMUL instructions missing from Sandybridge scheduler model
https://bugs.llvm.org/show_bug.cgi?id=36084 Bug ID: 36084 Summary: [X86] IMUL instructions missing from Sandybridge scheduler model Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: craig.top...@gmail.com CC: llvm-bugs@lists.llvm.org -- 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
