[llvm-bugs] [Bug 48277] AF: `(isUnknownLocation() || isRegisterLocation()) && "location description already locked down"' failed
https://bugs.llvm.org/show_bug.cgi?id=48277 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from lab...@google.com --- Reverted in bce2ac9f6d3be. I should note that the DW_AT_location for the example in #1 is was broken even before this patch -- the patch just turned that into an assertion failure. :( -- 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 48280] New: ColumnLimit check for trailing comments alignment acts wrong for multi-byte UTF-8
https://bugs.llvm.org/show_bug.cgi?id=48280 Bug ID: 48280 Summary: ColumnLimit check for trailing comments alignment acts wrong for multi-byte UTF-8 Product: clang Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: seroburomalino...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org .clang-format: AlignTrailingComments: true ColumnLimit: 80 What we have upon clang-format: int a_short; // some 1-byte UTF8 comment with some good and neat info int a_veryverylong; // some one-byte UTF8 comment breaks correctly at 80 char // boundary int a_short_rus; // А теперь комментарии, например, на русском, 2-байта int a_veryverylong_rus; // Верхний коммент еще не превысил границу в 80, однако // уже отодвинут. Перенос, при этом, отрабатывает верно - What we should have: int a_short; // some 1-byte UTF8 comment with some good info int a_veryverylong; // some one-byte UTF8 comment breaks correctly at 80 char // boundary int a_short_rus; // А теперь комментарии, например, на русском, 2-байта int a_veryverylong_rus; // Верхний коммент еще не превысил границу в 80, однако // уже отодвинут. Перенос, при этом, отрабатывает верно - Russian trailing comments go as UTF-8 2-byte characters, and, obviously, clang-format counts their length as raw byte count when checking if line is exceeded. As a result, comments fall back closer to code, while still having enough space for being aligned. This is relevant only for trailing comment alignment tirgger check. Line break upon exceeding 80 character limit works correctly for multi-byte characters. -- 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 48279] wrong code with "-sroa -loop-unroll -dse"
https://bugs.llvm.org/show_bug.cgi?id=48279 Florian Hahn changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME CC||florian_h...@apple.com --- Comment #1 from Florian Hahn --- I tried to reproduce the failure as suggested, but could not do so with current trunk of now (6b74eabfddbc6629adbf6358f8e78893c4ee1d12). Could you check and see if you can still reproduce the issue with current trunk? If so, please re-open the issue and attach the LLVM IR that is passed to opt as well. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48281] New: defaulted operator<=> triggers -Wzero-as-null-pointer-constant
https://bugs.llvm.org/show_bug.cgi?id=48281 Bug ID: 48281 Summary: defaulted operator<=> triggers -Wzero-as-null-pointer-constant Product: clang Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: C++2a Assignee: unassignedclangb...@nondot.org Reporter: georg.sch...@emocean.io CC: blitzrak...@gmail.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 24201 --> https://bugs.llvm.org/attachment.cgi?id=24201&action=edit Compile using "clang++ -std=c++20" Comparing two objects of a class or strut using <, >, <=, or >= results in the warning "zero as null pointer constant" if the class has a defaulted operator<=> (either friend or member). To reproduce, compile the attached file with "clang++ -std=c++20" Tested on Ubuntu 20.04 on WSL, using clang-11 package from http://apt.llvm.org/focal/: > clang++ -version Ubuntu clang version 11.0.1-++20201121072613+973b95e0a84-1~exp1~20201121063226.132 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin -- 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 48279] wrong code with "-sroa -loop-unroll -dse"
https://bugs.llvm.org/show_bug.cgi?id=48279 suochenyao changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- 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 48282] New: --cref on ld.lld writes the cref table to stdout even with -Map=filename
https://bugs.llvm.org/show_bug.cgi?id=48282
Bug ID: 48282
Summary: --cref on ld.lld writes the cref table to stdout even
with -Map=filename
Product: lld
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedb...@nondot.org
Reporter: j...@transactionware.com
CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com
Created attachment 24204
--> https://bugs.llvm.org/attachment.cgi?id=24204&action=edit
Patch to use the file from -Map as a target for --cref output.
The --cref option on ld.lld only seems to write to stdout, ignoring the
-Map=filename option. This is a change from GNU ld.
To reproduce, compile and link any code with --cref, for example:
echo 'int main() { return 0; }' > test.c
cc -Wl,-Map=test.map -Wl,--cref test.c
The cross reference table is emitted on stdout instead of being written to
test.map.
A patch (against the lld imported into the FreeBSD 12.2 tree) that resolves the
issue for me 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] [Bug 48283] New: Missing _InterlockedCompareExchange128 intrinsic functions for ARM64
https://bugs.llvm.org/show_bug.cgi?id=48283 Bug ID: 48283 Summary: Missing _InterlockedCompareExchange128 intrinsic functions for ARM64 Product: clang Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: zufu...@163.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk split from https://bugs.llvm.org/show_bug.cgi?id=47099 See https://docs.microsoft.com/en-us/cpp/intrinsics/interlockedcompareexchange128?view=msvc-160 _InterlockedCompareExchange128, _InterlockedCompareExchange128_acq, _InterlockedCompareExchange128_nf and _InterlockedCompareExchange128_rel are missing from intrin.h for ARM64. _InterlockedCompareExchange128_nf is used by Microsoft STL header for ARM64, see https://github.com/microsoft/STL/blob/master/stl/inc/atomic#L483 and https://github.com/microsoft/STL/issues/1491. -- 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 47390] [LoopVectorize] Assertion `isa(UI) && "Expected LCSSA form"' failed.
https://bugs.llvm.org/show_bug.cgi?id=47390 Lidiya Pavlovna Kryukova changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #7 from Lidiya Pavlovna Kryukova --- Works for me. I checked it on the test from the bug point, and also did the check on the large original test. Thank you -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47390] [LoopVectorize] Assertion `isa(UI) && "Expected LCSSA form"' failed.
https://bugs.llvm.org/show_bug.cgi?id=47390 ayal.z...@intel.com changed: What|Removed |Added Resolution|WORKSFORME |FIXED Fixed By Commit(s)||rG32d9a386bf8f -- 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 23059 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::Stmt::getBeginLoc
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 23059 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::Stmt::getBeginLoc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23059#c2 ClusterFuzz testcase 516271395840 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011230606:202011240611 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] [Bug 48285] New: [Hexagon] Add support for ISD::SMAX/SMIN/UMAX/UMIN instead of custom dag patterns
https://bugs.llvm.org/show_bug.cgi?id=48285 Bug ID: 48285 Summary: [Hexagon] Add support for ISD::SMAX/SMIN/UMAX/UMIN instead of custom dag patterns Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: Hexagon Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: kparz...@quicinc.com, llvm-bugs@lists.llvm.org Hexagon currently lowers integer signed/unsigned min/max ops using custom icmp+select patterns, but it could use the generic ISD opcodes. -- 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 27821 in oss-fuzz: llvm:clang-fuzzer: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible OS-Linux Proj-llvm Engine-honggfuzz Reported-2020-11-24 Type: Bug New issue 27821 by ClusterFuzz-External: llvm:clang-fuzzer: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27821 Detailed Report: https://oss-fuzz.com/testcase?key=4644565590736896 Project: llvm Fuzzing Engine: honggfuzz Fuzz Target: clang-fuzzer Job Type: honggfuzz_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a clang::Preprocessor::AnnotatePreviousCachedTokens clang::Parser::ParseOptionalCXXScopeSpecifier Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=honggfuzz_asan_llvm&revision=202008230608 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4644565590736896 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 27822 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-11-24 Type: Bug New issue 27822 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27822 Detailed Report: https://oss-fuzz.com/testcase?key=4692821573107712 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd9d9e0bf8 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=202010250629:202010260620 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4692821573107712 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 27823 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-11-24 Type: Bug New issue 27823 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27823 Detailed Report: https://oss-fuzz.com/testcase?key=4807434813833216 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd3de46e60 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::HandleDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202010190618:202010200603 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4807434813833216 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 48284] clang-analyzer-cplusplus.NewDeleteLeaks false positive
https://bugs.llvm.org/show_bug.cgi?id=48284 Eugene Zelenko changed: What|Removed |Added Product|clang-tools-extra |clang Assignee|unassignedclangbugs@nondot. |dcough...@apple.com |org | CC||dcough...@apple.com, ||eugene.zele...@gmail.com, ||llvm-bugs@lists.llvm.org Component|clang-tidy |Static Analyzer -- 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 48286] New: Not treating unions with at least one literal member as literal
https://bugs.llvm.org/show_bug.cgi?id=48286
Bug ID: 48286
Summary: Not treating unions with at least one literal member
as literal
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++11
Assignee: unassignedclangb...@nondot.org
Reporter: ant.bikin...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Clang fails to compile the following code:
std::optional unpopulated{};
The reduced example is:
template
struct A {
union {
char c = 0;
T t;
};
};
constexpr A unpopulated{};
The error clang emits is:
error: constexpr variable cannot have non-literal type 'const A'
constexpr A unpopulated{};
^
note: 'A' is not literal because it has data member '' of
non-literal type 'union (anonymous union at ...)'
A relevant section from the Standard (unless I'm missing another one):
[6.8.1.10]
A type is a literal type if it is:
- ...
- if it is a union, at least one of its non-static data members is of
non-volatile literal type, and ...
gcc succeeds to compile this example.
--
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 27842 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: (T->isIntegralType(Context) || T->isEnumeralType()) && "Integral type required!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-11-24 Type: Bug New issue 27842 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: (T->isIntegralType(Context) || T->isEnumeralType()) && "Integral type required!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27842 Detailed Report: https://oss-fuzz.com/testcase?key=5745168430661632 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (T->isIntegralType(Context) || T->isEnumeralType()) && "Integral type required!" isRepresentableIntegerValue clang::Sema::CheckEnumConstant Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011230606:202011240611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5745168430661632 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 25355 in oss-fuzz: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokens
Updates: Labels: Deadline-Approaching Comment #1 on issue 25355 by sheriffbot: llvm:clang-format-fuzzer: Stack-overflow in unsigned int clang::format::AlignTokenshttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25355#c1 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] [Bug 47430] Missing fold &a[i] - &a[j] => i - j
https://bugs.llvm.org/show_bug.cgi?id=47430 Sanjay Patel changed: What|Removed |Added Fixed By Commit(s)||ab29f09, 678b9c5 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Sanjay Patel --- Re-did the wrapping flags patch: https://reviews.llvm.org/rGab29f091eb64 And re-arranged the folds (we still miss the example in comment 3): https://reviews.llvm.org/rG678b9c5dde0d So that should take care of the problem in the description. -- 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 47425] return type for isnan instrinsic math function causes problem in conditional
https://bugs.llvm.org/show_bug.cgi?id=47425 Nichols A. Romero changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48287] New: atomic.cpp.o fails to compile with MUSL support enabled
https://bugs.llvm.org/show_bug.cgi?id=48287 Bug ID: 48287 Summary: atomic.cpp.o fails to compile with MUSL support enabled Product: new-bugs Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: vto...@googlemail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24205 --> https://bugs.llvm.org/attachment.cgi?id=24205&action=edit various log files and CMakeCache.txt build node: * X86 PC * Linux 5.9.11 * userland package distro: Debian * toolchain: lvm-11 (from distro - https://packages.debian.org/source/bullseye/llvm-toolchain-11) * CMake: 3.19.1 (self-compiled) _ trying to compile llvm-11 from source with LIBCXX_HAS_MUSL_LIBC=1 fails early on. Unless being a red herring it seems atomic.cpp.o fails to compile - see the attached build log as from line 1603 onwards -- 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 47777] Merge equally named output sections in linker scripts
https://bugs.llvm.org/show_bug.cgi?id=4 Fangrui Song changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #4 from Fangrui Song --- https://sourceware.org/pipermail/binutils/2020-November/114271.html Seems that the gold/LLD behavior is fine. -- 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 48288] New: copysign.cpp.o fails to compile
https://bugs.llvm.org/show_bug.cgi?id=48288 Bug ID: 48288 Summary: copysign.cpp.o fails to compile Product: new-bugs Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: vto...@googlemail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24206 --> https://bugs.llvm.org/attachment.cgi?id=24206&action=edit various log files and CMakeCache.txt build node: * X86 PC * Linux 5.9.11 * userland package distro: Debian * toolchain: lvm-11 (from distro - https://packages.debian.org/source/bullseye/llvm-toolchain-11) * CMake: 3.19.1 (self-compiled) _ trying to compile llvm-11 (.0.0) from source with LLVM_ENABLE_MODULES=1 fails early on. It seems that copysign.cpp.o fails to compile - see the attached build log (as from line 15568 onwards) -- 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 48289] New: Driver/hip-toolchain-rdc-static-lib.hip fails on Windows
https://bugs.llvm.org/show_bug.cgi?id=48289 Bug ID: 48289 Summary: Driver/hip-toolchain-rdc-static-lib.hip fails on Windows Product: clang Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: tstel...@redhat.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk This test is failing on the Windows test runners used for Github Actions. Here is an example log of one of the failures: https://github.com/tstellar/llvm-project/pull/240/checks?check_run_id=1445123556 -- 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 48290] New: ExampleClangLoopProtoFuzzer.cpp.o fails to compile
https://bugs.llvm.org/show_bug.cgi?id=48290 Bug ID: 48290 Summary: ExampleClangLoopProtoFuzzer.cpp.o fails to compile Product: new-bugs Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: vto...@googlemail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 24207 --> https://bugs.llvm.org/attachment.cgi?id=24207&action=edit various log files and CMakeCache.txt build node: * X86 PC * Linux 5.9.11 * userland package distro: Debian * toolchain: lvm-11 (from distro - https://packages.debian.org/source/bullseye/llvm-toolchain-11) * CMake: 3.19.1 (self-compiled) _ trying to compile llvm-11 (.0.0) from source with CLANG_ENABLE_PROTO_FUZZER=1 fails. It seems that ExampleClangLoopProtoFuzzer.cpp.o fails to compile - see the attached build log (as from line 26395 onwards) -- 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 39485] Flag flip for Hvx loop vectorizer broke Halide
https://bugs.llvm.org/show_bug.cgi?id=39485 Alina Sbirlea changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #9 from Alina Sbirlea --- I think this is obsolete. -- 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48271, which changed state. Bug 48271 Summary: backport c58674df147ac0e to 11.0 https://bugs.llvm.org/show_bug.cgi?id=48271 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 48271] backport c58674df147ac0e to 11.0
https://bugs.llvm.org/show_bug.cgi?id=48271 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|c58674df147ac0e |c58674df147ac0e 3e8d9807d66 --- Comment #3 from Tom Stellard --- Merged: 3e8d9807d66 -- 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 48007] Backport 0f60bcc36c34522618bd1425a45f8c6006568fb6 to 11.0.1
https://bugs.llvm.org/show_bug.cgi?id=48007 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|0f60bcc36c34522618bd1425a45 |0f60bcc36c34522618bd1425a45 |f8c6006568fb6 |f8c6006568fb6 |f2c6bfa350de142e4d63808d033 |f2c6bfa350de142e4d63808d033 |35f69bd136d6a |35f69bd136d6a |9573c9f2a363da71b2c07a3add4 |9573c9f2a363da71b2c07a3add4 |e52721e6028a0 |e52721e6028a0 bbe6cbbed8c ||aac36687f79 a1e0363c740 Status|NEW |RESOLVED --- Comment #9 from Tom Stellard --- Merged: a1e0363c740 -- 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48007, which changed state. Bug 48007 Summary: Backport 0f60bcc36c34522618bd1425a45f8c6006568fb6 to 11.0.1 https://bugs.llvm.org/show_bug.cgi?id=48007 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 48291] New: Typo: CLANG_DEFAULT_RTLIBS should be CLANG_DEFAULT_RTLIB
https://bugs.llvm.org/show_bug.cgi?id=48291 Bug ID: 48291 Summary: Typo: CLANG_DEFAULT_RTLIBS should be CLANG_DEFAULT_RTLIB Product: clang Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: xksz...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk https://github.com/llvm/llvm-project/blob/6bd01b8184de93979756331c71af69b422f71103/clang/CMakeLists.txt#L285 Should be RTLIB without S. -- 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 48292] New: [aarch64] Inefficient code in __builtin_mul_overflow with unsigned < 32 bits
https://bugs.llvm.org/show_bug.cgi?id=48292
Bug ID: 48292
Summary: [aarch64] Inefficient code in __builtin_mul_overflow
with unsigned < 32 bits
Product: libraries
Version: 10.0
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: AArch64
Assignee: unassignedb...@nondot.org
Reporter: husseyde...@gmail.com
CC: arnaud.degrandmai...@arm.com,
llvm-bugs@lists.llvm.org, smithp...@googlemail.com,
ties.st...@arm.com
Given the following C code:
bool umul16_overflow(uint16_t a, uint16_t b, uint16_t *result)
{
return __builtin_mul_overflow(a,b,result);
}
aarch64 clang 10.0.1 -O2:
umul16_overflow:
// Cast args
and w9, w1, #0x
and w10, w0, #0x
// 16-bit to 32-bit long multiply
mul w9, w10, w9
// Store upper 16 bits in w10
lsr w10, w9, #16
// Store zero in x8??
mov x8, xzr
// Check if upper 16 bits (w10) are non-zero
cmp w10, #0
csetw10, ne
// Check if zero (x8) is non-zero??
// w8 = 0
cmp x8, #0
csetw8, ne
// Or the result against zero??
orr w0, w10, w8
// Store
strhw9, [x2]
ret
I have no idea what x8 is being used for here, it will always be zero. This is
the code without the redundant instructions:
umul16_overflow:
// Cast args
and w8, w1, #0x
and w9, w0, #0x
// 16-bit to 32-bit long multiply
mul w8, w9, w8
// Store upper 16 bits in w9
lsr w9, w8, #16
// Check if the upper 16 bits (w9) are non-zero
cmp w9, #0
csetw0, ne
// Store
strhw9, [x2]
ret
Note that we could simplify this even further by using cmp more creatively, but
this appears to be a different issue.
umul16_overflow:
// Cast args
and w8, w1, #0x
and w9, w0, #0x
// 16-bit to 32-bit long multiply
mul w8, w9, w8
// Check if the upper 16 bits are non-zero
cmp wzr, w8, lsr #16
csetw0, ne
// Store
strhw8, [x2]
ret
--
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
