[llvm-bugs] [Bug 45368] c++2a: string::reserve still shrinks capacity (P0966)
https://bugs.llvm.org/show_bug.cgi?id=45368 Marek Kurdej changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Marek Kurdej --- Fixed by commit https://reviews.llvm.org/rG841132efda2157c5f9e07cf31469470a6481ffd9. -- 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 27686 in oss-fuzz: llvm: Fuzzing build failure
Comment #1 on issue 27686 by ClusterFuzz-External: llvm: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27686#c1 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-74164a1d-9661-4aef-be5b-94cba6799865.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 48293] llvm-strip produces malformed binaries on ARM Darwin
https://bugs.llvm.org/show_bug.cgi?id=48293 Yi Kong changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Yi Kong --- Okay, found out the cause is corrupted code signature. Not an issue with llvm-strip itself. -- 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 47486] Unreported changes from rewriteLoopExitValues
https://bugs.llvm.org/show_bug.cgi?id=47486 David Stenberg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from David Stenberg --- (In reply to David Stenberg from comment #2) > I uploaded a proposed patch for this: https://reviews.llvm.org/D91153 Landed as 384996f9e18ff3b7fa35b2083bf352c64b05c7bc. -- 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] Missing _InterlockedCompareExchange128 intrinsic functions for ARM64
https://bugs.llvm.org/show_bug.cgi?id=48283 Zufu Liu changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||https://reviews.llvm.org/rG ||1e843a987d847da48aaf41801b7 ||9cfb364937e8f 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 48308] New: Crash in OpenMP semantic check with do while in parallel
https://bugs.llvm.org/show_bug.cgi?id=48308 Bug ID: 48308 Summary: Crash in OpenMP semantic check with do while in parallel Product: flang Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: Frontend Assignee: unassignedb...@nondot.org Reporter: kiranchandramo...@gmail.com CC: david.tr...@arm.com, jper...@nvidia.com, kirankuma...@gmail.com, llvm-bugs@lists.llvm.org, sscalp...@nvidia.com The following code crashes with OpenMP semantics check. subroutine s(x,i) real :: x(:) integer :: i !$omp parallel firstprivate(i) do while (i>0) x(i) = i i = i - 1 end do !$omp end parallel end subroutine -- 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 48309] New: Request backport of 3 SVE PCS fixes for 11.0.1
https://bugs.llvm.org/show_bug.cgi?id=48309 Bug ID: 48309 Summary: Request backport of 3 SVE PCS fixes for 11.0.1 Product: libraries Version: 11.0 Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: Backend: AArch64 Assignee: unassignedb...@nondot.org Reporter: cullen.rho...@arm.com CC: arnaud.degrandmai...@arm.com, llvm-bugs@lists.llvm.org, sander.desma...@arm.com, smithp...@googlemail.com, ties.st...@arm.com Blocks: 47800 Created attachment 24215 --> https://bugs.llvm.org/attachment.cgi?id=24215&action=edit Zip containing the 3 patches Hi, would it be possible to backport the following patches to 11.0.1? [1] af57a0838eba528c2e5bd805d92c611435fca0d8 [SVE] Add fatal error when running out of registers for SVE tuple call arguments [2] cea69fa4dcc4fcf3be62dba49ad012879d89377d [SVE] Add fatal error for unnamed SVE variadic arguments [3] c87bd2d8eb378d152f2b6bde4cb088ad390a676c [AArch64] Implement .variant_pcs directive The first two patches introduce fatal errors for gaps in the SVE calling convention support. These apply cleanly but the first one required some minor changes to remove a redundant operand from a test that caused it to fail. The last patch fixes lazy binding support for SVE, which was mentioned as incomplete in the Clang 11.0.0 release notes. This didn't apply cleanly unfortunately, but I've attached a zip file containing the 3 patches and verified these can be applied on the llvmorg-11.0.1-rc1 branch (commit 12c4c6cd770a1651676560924ff77c9e4b383848) with: git am 0001-SVE-Add-fatal-error-when-running-out-of-registers-fo.patch 0002-SVE-Add-fatal-error-for-unnamed-SVE-variadic-argumen.patch 0003-AArch64-Implement-.variant_pcs-directive.patch Let me know if you have any issues or questions, Thanks, Cullen Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=47800 [Bug 47800] [meta] 11.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] Issue 27939 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::Stmt::getBeginLoc
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 Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-11-26 Type: Bug New issue 27939 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::Stmt::getBeginLoc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27939 Detailed Report: https://oss-fuzz.com/testcase?key=5160121566756864 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff040c1fc8 Crash State: clang::Stmt::getBeginLoc Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=202003230248:202003250252 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5160121566756864 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 27942 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-guard_widening: Heap-use-after-free in llvm::Value::setValueName
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 Security_Severity-High Reported-2020-11-27 Type: Bug-Security New issue 27942 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-guard_widening: Heap-use-after-free in llvm::Value::setValueName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27942 Detailed Report: https://oss-fuzz.com/testcase?key=5720028133195776 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-guard_widening Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash Address: 0x621094b0 Crash State: llvm::Value::setValueName llvm::LLVMContextImpl::~LLVMContextImpl llvm::LLVMContext::~LLVMContext Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011250612:202011260600 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5720028133195776 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 48311] New: [DebugInfo] Overlapping fragment crash at -g -O3 -mllvm -enable-partial-inlining
https://bugs.llvm.org/show_bug.cgi?id=48311
Bug ID: 48311
Summary: [DebugInfo] Overlapping fragment crash at -g -O3
-mllvm -enable-partial-inlining
Product: libraries
Version: trunk
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: DebugInfo
Assignee: unassignedb...@nondot.org
Reporter: sourav0...@gmail.com
CC: apra...@apple.com, jdevliegh...@apple.com,
jeremy.morse.l...@gmail.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com, v...@apple.com
$ clang -g -O3 -mllvm -enable-partial-inlining test.c
^~~
llvm/lib/CodeGen/AsmPrinter/DwarfExpression.cpp:638: void
llvm::DwarfExpression::addFragmentOffset(const llvm::DIExpression*): Assertion
`FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"'
failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0. Program arguments: /home/sourabh/mirror-1. parser at end of
file
2. Code generation
3. Running pass 'Function Pass Manager' on module 'test.c'.
4. Running pass 'X86 Assembly Printer' on function '@k.1.if.then'
...
Reduced test case:
int i();
int m();
int l();
int n(int, int*);
struct a {
struct {
long b;
int volatile c;
} d;
};
long e;
int j;
int f() {
volatile int g;
do {
if (g)
return 0;
struct a h;
h.d.c = e = i();
} while (1);
}
void k() {
if (l()) {
int c = f();
while (0 == c) {
m();
f() <= n(j, &c);
}
}
}
void p() { k(); }
For simplifying reproducibity, can also be reproduced as:
$ clang -g -O3 test.c -S -emit-llvm
$ opt -partial-inliner test.ll -S | llc >/dev/null
--CRASH--
--
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
