[llvm-bugs] [Bug 41521] New: Compiler crash in semantic analyser
https://bugs.llvm.org/show_bug.cgi?id=41521 Bug ID: 41521 Summary: Compiler crash in semantic analyser Product: clang Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: krzysio.ku...@wp.pl CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21789 --> https://bugs.llvm.org/attachment.cgi?id=21789&action=edit preprocessed file Compiled with `clang++ -std=c++17 ./main.cpp` -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41520] New: -Oz significantly increase binary size comparing to -Os, often even -O2
https://bugs.llvm.org/show_bug.cgi?id=41520 Bug ID: 41520 Summary: -Oz significantly increase binary size comparing to -Os, often even -O2 Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: vitalyb...@google.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Here is a reproducer on one of reprocessed llvm files https://reviews.llvm.org/D60807 Size of Oz object is 3x of Os. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41359] [TargetLowering] Improve descriptions for preferShiftsToClearExtremeBits and shouldFoldShiftPairToMask
https://bugs.llvm.org/show_bug.cgi?id=41359 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Simon Pilgrim --- (In reply to Eli Friedman from comment #5) > Sure, that looks fine. Cheers, committed at rL358526 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41519] New: Out-of-bounds check for pointer arith
https://bugs.llvm.org/show_bug.cgi?id=41519 Bug ID: 41519 Summary: Out-of-bounds check for pointer arith Product: new-bugs Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: m.horlb...@tu-braunschweig.de CC: htmldevelo...@gmail.com, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41101] [EarlyCSE] recognize swapped form of selects
https://bugs.llvm.org/show_bug.cgi?id=41101 Sanjay Patel changed: 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41518] Incorrect feature set for Exynos M4
https://bugs.llvm.org/show_bug.cgi?id=41518 Evandro Menezes changed: What|Removed |Added Blocks||41221 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Evandro Menezes --- Fixed by r356698. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=41221 [Bug 41221] [meta] 8.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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41518, which changed state. Bug 41518 Summary: Incorrect feature set for Exynos M4 https://bugs.llvm.org/show_bug.cgi?id=41518 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41518] New: Incorrect feature set for Exynos M4
https://bugs.llvm.org/show_bug.cgi?id=41518 Bug ID: 41518 Summary: Incorrect feature set for Exynos M4 Product: tools Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: llc Assignee: unassignedb...@nondot.org Reporter: e.mene...@samsung.com CC: llvm-bugs@lists.llvm.org The feature set for Exynos M4 specified the incorrect particular feature for FP16. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40364] Handling of extern globals in WebAssembly
https://bugs.llvm.org/show_bug.cgi?id=40364 Sam Clegg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sam Clegg --- This should be ready to test in llvm trunk now. When you build with "-fPIC" and link with "-shared" you should not see external globals and function accessed by GOT.func.foo and GOT.mem.foo imported globals. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41516] New: -Wsign-conversion does not warn on uint64_t to int8_t, int16_t, or int32_t implicit conversions
https://bugs.llvm.org/show_bug.cgi?id=41516 Bug ID: 41516 Summary: -Wsign-conversion does not warn on uint64_t to int8_t, int16_t, or int32_t implicit conversions Product: clang Version: unspecified Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: jeffersoncarpent...@gmail.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 21788 --> https://bugs.llvm.org/attachment.cgi?id=21788&action=edit Program that does not raise sign conversion warning Compile the attachment with clang++ -std=c++17 -Wsign-conversion ./test.cpp -o test Implicit signedness conversions form uint64_t to numerous integer types are not warned. Only the conversion from uint64_t to int64_t is warned. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41515] New: Improve the behaviour of llvm-nm when symbols with invalid section indexes are encountered
https://bugs.llvm.org/show_bug.cgi?id=41515 Bug ID: 41515 Summary: Improve the behaviour of llvm-nm when symbols with invalid section indexes are encountered Product: tools Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: llvm-nm Assignee: unassignedb...@nondot.org Reporter: snortot...@gmail.com CC: llvm-bugs@lists.llvm.org When a symbol with an invalid section index is encountered, llvm-nm does not print an error. It simply omits the symbol from the printable symbol list. The desired behaviour can likely be achieved by altering the branch in dumpSymbolNamesFromObject() when getSymbolAddress() returns an error, either to add the symbol to the printable symbol list or print an error. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41514] New: [Parser] Pragma inside statement causes error
https://bugs.llvm.org/show_bug.cgi?id=41514
Bug ID: 41514
Summary: [Parser] Pragma inside statement causes error
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: l...@meinersbur.de
CC: hfin...@anl.gov, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
The following source does not compile:
int main() {
return
#pragma STDC FENV_ACCESS OFF
0;
}
$ clang test.c
test.c:5:14: error: expected expression
#pragma STDC FENV_ACCESS OFF
^
1 error generated.
While this one does:
int main() {
#pragma STDC FENV_ACCESS OFF
return 0;
}
$ clang test.c
The reason is that the #pragma inserts an annotation token into the
preprocessor's token stream. This annotation is only handled before a new
statement is expected (method
Parser::ParseStatementOrDeclarationAfterAttributes), but not within e.g.
expressions.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41513] New: [yaml2obj] will crash when reading a yaml file which only contains comments.
https://bugs.llvm.org/show_bug.cgi?id=41513 Bug ID: 41513 Summary: [yaml2obj] will crash when reading a yaml file which only contains comments. Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: higuox...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org yaml2obj will crash if it reads a yaml file only contains comments. e.g. ``` $ cat empty.yaml # some comment $ yaml2obj empty.yaml Stack dump: 0. Program arguments: /Users/cat/Workspace/llvm/llvm-tools-lld-build/bin/yaml2obj empty.yaml 0 yaml2obj 0x000106d96138 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 40 1 yaml2obj 0x000106d952b5 llvm::sys::RunSignalHandlers() + 85 2 yaml2obj 0x000106d967a8 SignalHandler(int) + 264 3 libsystem_platform.dylib 0x7fffbf796b3a _sigtramp + 26 4 libsystem_platform.dylib 0x7fff58f65060 _sigtramp + 2575099200 5 yaml2obj 0x000106d4d1fd llvm::yaml::MappingTraits::mapping(llvm::yaml::IO&, llvm::yaml::YamlObjectFile&) + 141 6 yaml2obj 0x000106c9cc0c main + 892 7 libdyld.dylib0x7fffbf587235 start + 1 8 libdyld.dylib0x0002 start + 1084722638 [1]2847 segmentation fault ~/Workspace/llvm/llvm-tools-lld-build/bin/yaml2obj empty.yaml ``` -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35235] stable_sort() won't compile with function object that takes parameters by non-const reference
https://bugs.llvm.org/show_bug.cgi?id=35235 Marshall Clow (home) changed: What|Removed |Added Resolution|--- |INVALID Status|CONFIRMED |RESOLVED --- Comment #6 from Marshall Clow (home) --- As a result of LWG #3101, this is not a valid program (any more). I'm not going to post a rationale here, since Jonathan put a good one in the libstdc++ bug report. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41492] LLVM JIT generates invalid instructions for the CPU INTEL® PENTIUM® GOLD PROCESSOR 4415Y which is detected as being "Skylake"
https://bugs.llvm.org/show_bug.cgi?id=41492 Alexandre Bique changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12615 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: isImm() && "Wrong MachineOperand accessor"
Updates: Labels: Deadline-Approaching Comment #4 on issue 12615 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: isImm() && "Wrong MachineOperand accessor" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12615#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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 10631 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #8 on issue 10631 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS | | !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10631#c8 ClusterFuzz testcase 5768734862475264 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 10631 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out
Comment #7 on issue 10631 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS | | !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10631#c7 ClusterFuzz has detected this issue as fixed in range 201904150259:201904151909. Detailed report: https://oss-fuzz.com/testcase?key=5768734862475264 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: (!RS || !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out llvm::AArch64RegisterInfo::eliminateFrameIndex llvm::RegScavenger::spill Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130454 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904150259:201904151909 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5768734862475264 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14278 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output
Comment #2 on issue 14278 by tha...@google.com: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14278#c2 http://reviews.llvm.org/rL358491 should fix. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14247 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray
Comment #2 on issue 14247 by tha...@google.com: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14247#c2 https://reviews.llvm.org/D60774 should fix this. -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14278 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2019-04-16 Type: Bug New issue 14278 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::StructorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14278 Detailed report: https://oss-fuzz.com/testcase?key=5760141921615872 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::ms_demangle::StructorIdentifierNode::output llvm::ms_demangle::Demangler::memorizeIdentifier llvm::ms_demangle::Demangler::demangleTemplateInstantiationName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5760141921615872 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14210 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 14210 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14210#c3 ClusterFuzz testcase 5669082890764288 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14210 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output
Comment #2 on issue 14210 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Null-dereference READ in llvm::ms_demangle::ConversionOperatorIdentifierNode::output https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14210#c2 ClusterFuzz has detected this issue as fixed in range 201904150259:201904151909. Detailed report: https://oss-fuzz.com/testcase?key=5669082890764288 Project: llvm Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer Fuzz target binary: llvm-microsoft-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::ms_demangle::ConversionOperatorIdentifierNode::output llvm::ms_demangle::Demangler::memorizeIdentifier llvm::ms_demangle::Demangler::demangleTemplateInstantiationName Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904150259:201904151909 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5669082890764288 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41512] New: Conversion from int to XMM is handled inefficiently on SSE4
https://bugs.llvm.org/show_bug.cgi?id=41512 Bug ID: 41512 Summary: Conversion from int to XMM is handled inefficiently on SSE4 Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: spr...@yandex-team.ru CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com Created attachment 21786 --> https://bugs.llvm.org/attachment.cgi?id=21786&action=edit Proposed fix In attempt to swicth all our builds to SSE4 from SSSE3 we found out that code as simple as const __m128i lo = _mm_cvtsi32_si128(d0[value]); const __m128i hi = _mm_cvtsi32_si128(d0[value+1024]); val = _mm_add_epi64(val, _mm_unpacklo_epi64(lo, hi)); or const __m128i all = _mm_set_epi32(0, d0[value], 0, d0[value+1024]); val = _mm_add_epi64(val, all); When inlined into loop performs worse when compiled with -sse4.1 than with just -ssse3. The problem is that _mm_cvtsi32_si128() and _mm_set_epi32() both modeled via INSERT_VECTOR_ELT, and %13 = insertelement <4 x i32> , i32 %12, i32 0, !dbg !287 Lowered to single movd instruction prior to SSE4 and to xor+pinsrd on SSE4. https://gcc.godbolt.org/z/qY8nkO * Notice that in a kernel fucntion in 2nd case there are couple of movd's, but when used in loop it results in pair of pinsrd from memory into same register. This seems to me like poor instruction selection both from performance and code size standpopints. I suggset steering instruction selection for this idiomatic case of INSERT_VECTOR_ELT to SCALAR_TO_VECTOR. This will directly lead to movd emission. Proposed change to lib/Target/X86/X86ISelLowering.cpp is attached. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 10250 in oss-fuzz: llvm: Build failure
Comment #49 on issue 10250 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10250#c49 Friendly reminder that the the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-682a350f-a76b-4445-b398-162bdbb7b844.txt -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41486] lldb/source/Symbol/ArmUnwindInfo.cpp: 307: duplicate condition ?
https://bugs.llvm.org/show_bug.cgi?id=41486 Raphael Isemann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Raphael Isemann --- Fixed in r358479, thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41489] lldb/source/Core/Module.cpp: 3 * bad test ?
https://bugs.llvm.org/show_bug.cgi?id=41489 Raphael Isemann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Fixed By Commit(s)||r358477 Resolution|--- |FIXED --- Comment #4 from Raphael Isemann --- Fixed in r358477, thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41481] AddressSanitizer stack-use-after-scope false positive after r357452
https://bugs.llvm.org/show_bug.cgi?id=41481 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Hans Wennborg --- r358478. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
