[llvm-bugs] [Bug 40607] [ubsan] False positive object-size error in constructors of classes with multiple virtual inheritance
https://bugs.llvm.org/show_bug.cgi?id=40607 maic changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||mai...@live.de --- Comment #2 from maic --- Fixed between clang-9 and clang-11: $ clang++-11 -std=c++11 -O2 -fsanitize=object-size ./2.cpp && ./a.out $ clang++-9 -std=c++11 -O2 -fsanitize=object-size ./2.cpp && ./a.out 2.cpp:9:8: runtime error: constructor call on address 0x7ffc9fa7f7a8 with insufficient space for an object of type 'D' 0x7ffc9fa7f7a8: note: pointer points here 00 00 00 00 c1 11 00 00 a0 04 00 00 00 00 00 00 00 00 00 00 d0 3f e5 2d 5b 7f 00 00 02 00 00 00 ^ -- 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 51440] clang9 and clang10 got LLVM error: out of memory on compiling std::get<> calls with undefined sanitizer
https://bugs.llvm.org/show_bug.cgi?id=51440 maic changed: What|Removed |Added Resolution|--- |FIXED CC||mai...@live.de Status|NEW |RESOLVED --- Comment #1 from maic --- I was able to reproduce on clang-9, but I can no longer reproduce on clang-11 -- 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 43590] Compilation and run time failure with UBSan std::filesystem libstdc++fs
https://bugs.llvm.org/show_bug.cgi?id=43590 maic changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||mai...@live.de --- Comment #1 from maic --- I can't reproduce with clang-9. Is this still an issue? -- 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 51886] New: Wrong Version of libc++1, libc++abi1 & libunwind in LLVM's Ubuntu Hirsute "Development" Repo
https://bugs.llvm.org/show_bug.cgi?id=51886 Bug ID: 51886 Summary: Wrong Version of libc++1, libc++abi1 & libunwind in LLVM's Ubuntu Hirsute "Development" Repo Product: Packaging Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: deb packages Assignee: unassignedb...@nondot.org Reporter: tanishqban...@gmail.com CC: llvm-bugs@lists.llvm.org The llvmis supposed to provide version 14 of llvm, clang and other packages. But in case of libc++1, libc++abi1 & libunwind; it is currently providing version 12 with "apt install libc++1". (other packages are at version 14) Temporary Fix : install using "apt install libc++1-14-dev" and. Then create appropriate symlinks. Proposed Changes : Update the meta packages to automatically provide version 14 of libc++, libc++abi and libunwind. (I might have misspelled the exact package name, so ignore that please) -- 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 51887] New: Unambiguous use of operator==considered ambiguous.
https://bugs.llvm.org/show_bug.cgi?id=51887
Bug ID: 51887
Summary: Unambiguous use of operator==considered ambiguous.
Product: clang
Version: 12.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: qtom.boeh...@googlemail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
The following compiles fine with gcc, but with clang gives the error: "use of
overloaded operator '==' is ambiguous".
#include
template
bool operator==(T const&, T const&)
{
return false;
}
template
struct S
{
template
constexpr
bool operator==(S const&) const
{
return true;
}
};
int main()
{
auto i = S<0>{};
auto j = S<0>{};
assert(i == j);
}
--
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 51888] New: 32-bit pointer address space crashes in back-end
https://bugs.llvm.org/show_bug.cgi?id=51888
Bug ID: 51888
Summary: 32-bit pointer address space crashes in back-end
Product: libraries
Version: 12.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Backend: X86
Assignee: akhu...@google.com
Reporter: ararmi...@gmail.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, pengfei.w...@intel.com,
spatel+l...@rotateright.com
The following C++ code crashes in back-end with fatal error:
extern "C" {
extern int printf(const char *, ...);
}
const char c1[] = "foo1";
int main() {
const char* __ptr32 cp32[] = {c1};
printf("%s\n", cp32[0]);
}
run test with the following command:
clang test.cpp -S -target x86_64-windows-msvc -fms-extensions
Here is the crash:
fatal error: error in backend: Unsupported expression in static initializer:
addrspacecast (i8* getelementptr inbounds ([5 x i8], [5 x i8]* @c1, i64 0, i64
0) to i8 addrspace(270)*)
Stack dump:
0. Program arguments: clang test.cpp -S -target x86_64-windows-msvc
-fms-extensions
1. parser at end of file
2. Code generation
#0 0x55e67233ac8e llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/home/armine/llvm/release_build/bin/clang-10+0x1958c8e)
#1 0x55e6723389d4 llvm::sys::RunSignalHandlers()
(/home/armine/llvm/release_build/bin/clang-10+0x19569d4)
#2 0x55e672338c51 llvm::sys::CleanupOnSignal(unsigned long)
(/home/armine/llvm/release_build/bin/clang-10+0x1956c51)
#3 0x55e6722b4548 llvm::CrashRecoveryContext::HandleExit(int)
(/home/armine/llvm/release_build/bin/clang-10+0x18d2548)
#4 0x55e67233189b llvm::sys::Process::Exit(int)
(/home/armine/llvm/release_build/bin/clang-10+0x194f89b)
#5 0x55e67132cd87 LLVMErrorHandler(void*, std::__cxx11::basic_string, std::allocator > const&, bool)
(/home/armine/llvm/release_build/bin/clang-10+0x94ad87)
#6 0x55e6722badbb llvm::report_fatal_error(llvm::Twine const&, bool)
(/home/armine/llvm/release_build/bin/clang-10+0x18d8dbb)
#7 0x55e6722baf4d (/home/armine/llvm/release_build/bin/clang-10+0x18d8f4d)
#8 0x55e672db19f3 (/home/armine/llvm/release_build/bin/clang-10+0x23cf9f3)
#9 0x55e672db13c8 llvm::AsmPrinter::lowerConstant(llvm::Constant const*)
(/home/armine/llvm/release_build/bin/clang-10+0x23cf3c8)
#10 0x55e672db4c33 emitGlobalConstantImpl(llvm::DataLayout const&,
llvm::Constant const*, llvm::AsmPrinter&, llvm::Constant const*, unsigned long)
(/home/armine/llvm/release_build/bin/clang-10+0x23d2c33)
#11 0x55e672db4b0e emitGlobalConstantImpl(llvm::DataLayout const&,
llvm::Constant const*, llvm::AsmPrinter&, llvm::Constant const*, unsigned long)
(/home/armine/llvm/release_build/bin/clang-10+0x23d2b0e)
#12 0x55e672db7153
llvm::AsmPrinter::EmitGlobalVariable(llvm::GlobalVariable const*)
(/home/armine/llvm/release_build/bin/clang-10+0x23d5153)
#13 0x55e672db9a09 llvm::AsmPrinter::doFinalization(llvm::Module&)
(/home/armine/llvm/release_build/bin/clang-10+0x23d7a09)
#14 0x55e671cf46e5 llvm::FPPassManager::doFinalization(llvm::Module&)
(.localalias) (/home/armine/llvm/release_build/bin/clang-10+0x13126e5)
#15 0x55e671d021e0 llvm::legacy::PassManagerImpl::run(llvm::Module&)
(/home/armine/llvm/release_build/bin/clang-10+0x13201e0)
#16 0x55e67259b17c clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&,
clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout
const&, llvm::Module*, clang::BackendAction,
std::unique_ptr >)
(/home/armine/llvm/release_build/bin/clang-10+0x1bb917c)
#17 0x55e673197629
clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&)
(/home/armine/llvm/release_build/bin/clang-10+0x27b5629)
#18 0x55e673dcc8c1 clang::ParseAST(clang::Sema&, bool, bool)
(/home/armine/llvm/release_build/bin/clang-10+0x33ea8c1)
#19 0x55e672b72d39 clang::FrontendAction::Execute()
(/home/armine/llvm/release_build/bin/clang-10+0x2190d39)
#20 0x55e672b2a72b
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
(/home/armine/llvm/release_build/bin/clang-10+0x214872b)
#21 0x55e672c495eb
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
(/home/armine/llvm/release_build/bin/clang-10+0x22675eb)
#22 0x55e67132d424 cc1_main(llvm::ArrayRef, char const*,
void*) (/home/armine/llvm/release_build/bin/clang-10+0x94b424)
#23 0x55e67132b28a ExecuteCC1Tool(llvm::SmallVectorImpl&)
(/home/armine/llvm/release_build/bin/clang-10+0x94928a)
#24 0x55e6729f48c9 void llvm::function_ref::callback_fn
>, std::__cxx11::basic_string,
std::allocator >*, bool*) const::'lambda'()>(long)
(/home/armine/llvm/release_build/bin/clang-10+0x20128c9)
#25 0x55e6722b43c7
llvm::CrashRecoveryContext::RunSafely(llvm::function_ref)
(/home/armine/llvm/release_build/bin/clang-1
[llvm-bugs] [Bug 51886] Wrong Version of libc++1, libc++abi1 & libunwind in LLVM's Ubuntu Hirsute "Development" Repo
https://bugs.llvm.org/show_bug.cgi?id=51886 Tanishq Banyal 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 51889] New: error: comparison of distinct pointer types ('int *' and 'int * __ptr32')
https://bugs.llvm.org/show_bug.cgi?id=51889
Bug ID: 51889
Summary: error: comparison of distinct pointer types ('int *'
and 'int * __ptr32')
Product: clang
Version: 12.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Frontend
Assignee: akhu...@google.com
Reporter: ararmi...@gmail.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
1. cat test.cpp
extern "C"
int printf(const char *,...);
int* b = (int*)-1;
int main()
{
if (b == (int * __ptr32) -1)
printf("values are the same\n");
else
printf("values are different\n");
}
2. clang -fsyntax-only -target x86_64-windows-msvc -fms-extensions test.cpp
test.cpp:8:9: error: comparison of distinct pointer types ('int *' and 'int *
__ptr32')
if (b == (int * __ptr32) -1)
~ ^ ~~
1 error generated.
--
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 25725] Size-inefficient lowering of zero-memset
https://bugs.llvm.org/show_bug.cgi?id=25725 David Bolvansky changed: What|Removed |Added Fixed By Commit(s)||ff6b074674f0 Resolution|--- |FIXED CC||david.bolvan...@gmail.com Status|NEW |RESOLVED --- Comment #1 from David Bolvansky --- Fixed in LLVM 12. f: # @f mov eax, dword ptr [esp + 4] xorps xmm0, xmm0 movups xmmword ptr [eax + 48], xmm0 movups xmmword ptr [eax + 32], xmm0 movups xmmword ptr [eax + 16], xmm0 movups xmmword ptr [eax], xmm0 ret Testcase added in https://reviews.llvm.org/rGff6b074674f0. -- 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 51890] New: [C++4OpenCL] Issues with address-spaced destructors
https://bugs.llvm.org/show_bug.cgi?id=51890
Bug ID: 51890
Summary: [C++4OpenCL] Issues with address-spaced destructors
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: OpenCL
Assignee: unassignedclangb...@nondot.org
Reporter: olemarius.str...@arm.com
CC: anastasia.stul...@arm.com, llvm-bugs@lists.llvm.org
Here are some test cases that currently give an error in C++ for OpenCL, though
they should likely work.
Currently the simplest test case:
struct S {
~S() __global;
~S() __private;
};
void k() {
__private S s;
}
Is incorrect because it uses the global destructor (It always uses the first
destructor that's defined.
This also extends to many other situations, like inheritance:
struct A {
~A() __global = delete;
~A() __private = default;
};
struct S: public A {
~S() __private;
};
void k() {
__private S s;
}
Here trying to make a private variable fails because it thinks the destructor
of A is
deleted (because the first destructor is deleted), however if you reorder A's
destructors
it works, because it looks at the top one, which is not deleted.
Destructors are used in a lot of places, and address spaces aren't handled for
any of them,
so there are likely many more situations that are incorrect, but these are the
ones I've found specific cases for.
--
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 51505] [execute]binary compile with -O0 run diff to gcc -O0 on aarch64
https://bugs.llvm.org/show_bug.cgi?id=51505 David Spickett changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from David Spickett --- Fixed by https://reviews.llvm.org/D108755. -- 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 37904] u'ab' and U'ab' considered errors
https://bugs.llvm.org/show_bug.cgi?id=37904 Aaron Ballman changed: What|Removed |Added CC||aa...@aaronballman.com Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Aaron Ballman --- FWIW, C++ is exploring explicitly rejecting these constructs (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2362r2.pdf) and I expect WG14 to receive a similar proposal. I think it's reasonable for our implementation-defined behavior here to be to reject those constructs. In fact, we recently strengthened our handling of this in https://reviews.llvm.org/D106215 to also apply to L'ab' in addition to u'ab' and U'ab'. Closing this as WONTFIX, but if you know of a reason we *should* be allowing these constructs, please reopen with information about your use case. -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51688, which changed state. Bug 51688 Summary: Please backport c9948e9254fb to llvm13 https://bugs.llvm.org/show_bug.cgi?id=51688 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 51688] Please backport c9948e9254fb to llvm13
https://bugs.llvm.org/show_bug.cgi?id=51688 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)|c9948e9254fb|c9948e9254fb 635b7871de93 --- Comment #2 from Tom Stellard --- Merged: 635b7871de93 -- 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 51891] New: Cherry-pick 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 into release/13.x
https://bugs.llvm.org/show_bug.cgi?id=51891 Bug ID: 51891 Summary: Cherry-pick 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 into release/13.x Product: lld Version: unspecified Hardware: PC URL: https://github.com/llvm/llvm-project/commit/454f69bcc1 7e6451c926a2e7b708e900fc8fdcb8 OS: Linux Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: sedat.di...@gmail.com CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com Blocks: 51236 As reported in [1] this breaks LLD check-targets in these two tests... 1. ELF/compressed-debug-input.s 2. ELF/compressed-debug-input-err.s ...when you build for X86 and BPF targets on x86-64 Linux. Note: These tests fail when you have no PPC target enabled. The fix is to apply the commit from [2]: "[LLD] Add required ppc target to the test cases. NFC" Please cherry-pick this to release/13.x Git. Thanks. [1] https://lists.llvm.org/pipermail/llvm-dev/2021-September/152693.html [2] https://github.com/llvm/llvm-project/commit/454f69bcc17e6451c926a2e7b708e900fc8fdcb8 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51882] "fragment is larger than or outside of variable" and "fragment covers entire variable" with LTO
https://bugs.llvm.org/show_bug.cgi?id=51882 Eli Friedman changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Eli Friedman --- Yes, same thing as far as I can tell. *** This bug has been marked as a duplicate of bug 24923 *** -- 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 51893] New: llc crashes on NVPTX target when f80 parameters are passed by value.
https://bugs.llvm.org/show_bug.cgi?id=51893 Bug ID: 51893 Summary: llc crashes on NVPTX target when f80 parameters are passed by value. Product: libraries Version: 12.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Backend: PTX Assignee: unassignedb...@nondot.org Reporter: lightb...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 25268 --> https://bugs.llvm.org/attachment.cgi?id=25268&action=edit compile with llc to crash llc crashes when lowering f80 function arguments in the NVPTX kernel. I'd like to be able to pass these arguments to NVPTX functions. I can provide definitions for math ops that emulate the f80 instructions.. but still need to pass the parameters around. -- 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 51413] the C API for the dwarf debug info does not allow to link a global variable to a DI compilation unit
https://bugs.llvm.org/show_bug.cgi?id=51413 Basile.B changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Basile.B --- LLVMDIBuilderFinalize() does that. -- 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 51894] New: Merge b588f5d665aa01fe88921fe2ffb7256fdedfbfb0 into 13.0
https://bugs.llvm.org/show_bug.cgi?id=51894 Bug ID: 51894 Summary: Merge b588f5d665aa01fe88921fe2ffb7256fdedfbfb0 into 13.0 Product: clang Version: unspecified Hardware: All OS: OpenBSD Status: NEW Severity: release blocker Priority: P Component: Static Analyzer Assignee: dcough...@apple.com Reporter: b...@comstyle.com CC: dcough...@apple.com, llvm-bugs@lists.llvm.org Blocks: 51236 Please merge https://github.com/llvm/llvm-project/commit/b588f5d665aa01fe88921fe2ffb7256fdedfbfb0. [clang][scan-build] Use cc/c++ instead of gcc/g++ on OpenBSD. Modern versions of OpenBSD do not have gcc/g++ so scan-build out of the box is broken as is. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51895] New: Merge 3db959060546eef76b90733ccde80c75576a97ad into 13.0
https://bugs.llvm.org/show_bug.cgi?id=51895 Bug ID: 51895 Summary: Merge 3db959060546eef76b90733ccde80c75576a97ad into 13.0 Product: compiler-rt Version: unspecified Hardware: Other OS: OpenBSD Status: NEW Severity: release blocker Priority: P Component: builtins Assignee: unassignedb...@nondot.org Reporter: b...@comstyle.com CC: llvm-bugs@lists.llvm.org Blocks: 51236 Please merge https://github.com/llvm/llvm-project/commit/3db959060546eef76b90733ccde80c75576a97ad. [compiler-rt] Implement __clear_cache() on OpenBSD/riscv64. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51847] 13.0.0-rc3 regression: GWP-ASan-i386 :: backtrace.c failure (segv?)
https://bugs.llvm.org/show_bug.cgi?id=51847 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|210d72e9d6b4|210d72e9d6b4 d811546f803c Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Tom Stellard --- Merged: d811546f803c -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51847, which changed state. Bug 51847 Summary: 13.0.0-rc3 regression: GWP-ASan-i386 :: backtrace.c failure (segv?) https://bugs.llvm.org/show_bug.cgi?id=51847 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] Issue 38921 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::makeDeclVisibleInContextImpl
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-2021-09-18 Type: Bug New issue 38921 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::makeDeclVisibleInContextImpl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=38921 Detailed Report: https://oss-fuzz.com/testcase?key=6253750457597952 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe83990fe4 Crash State: clang::DeclContext::makeDeclVisibleInContextImpl clang::DeclContext::buildLookupImpl clang::DeclContext::buildLookup Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202108010605:202108020602 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6253750457597952 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 51774] Attempt to build memory sanitized libc++ with compiler-rt and libunwind fails
https://bugs.llvm.org/show_bug.cgi?id=51774 Nehal J Wani changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nehal J Wani --- Fix has been reviewed and merged. xref: https://reviews.llvm.org/D109342 xref: https://github.com/llvm/llvm-project/commit/1613ab8a -- 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 51886] Wrong Version of libc++1, libc++abi1 & libunwind in LLVM's Ubuntu Hirsute "Development" Repo
https://bugs.llvm.org/show_bug.cgi?id=51886 Tanishq Banyal changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- 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 51880] [OpenMP] Merge 41a6b50c2596 into 13.0.0
https://bugs.llvm.org/show_bug.cgi?id=51880 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|41a6b50c2596|41a6b50c2596 8d78ac26f475 --- Comment #1 from Tom Stellard --- Merged: 8d78ac26f475 -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51880, which changed state. Bug 51880 Summary: [OpenMP] Merge 41a6b50c2596 into 13.0.0 https://bugs.llvm.org/show_bug.cgi?id=51880 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 51891] Cherry-pick 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 into release/13.x
https://bugs.llvm.org/show_bug.cgi?id=51891 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|454f69bcc17e6451c926a2e7b70 |454f69bcc17e6451c926a2e7b70 |8e900fc8fdcb8 |8e900fc8fdcb8 6aa054242d60 --- Comment #1 from Tom Stellard --- Merged: 6aa054242d60 -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51891, which changed state. Bug 51891 Summary: Cherry-pick 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 into release/13.x https://bugs.llvm.org/show_bug.cgi?id=51891 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 51895] Merge 3db959060546eef76b90733ccde80c75576a97ad into 13.0
https://bugs.llvm.org/show_bug.cgi?id=51895 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|3db959060546eef76b90733ccde |3db959060546eef76b90733ccde |80c75576a97ad |80c75576a97ad 6a5ccb2ec438 Status|NEW |RESOLVED --- Comment #1 from Tom Stellard --- Merged: 6a5ccb2ec438 -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51895, which changed state. Bug 51895 Summary: Merge 3db959060546eef76b90733ccde80c75576a97ad into 13.0 https://bugs.llvm.org/show_bug.cgi?id=51895 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] Issue 38928 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::BuildCXXNestedNameSpecifier
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-2021-09-18 Type: Bug New issue 38928 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::BuildCXXNestedNameSpecifier https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=38928 Detailed Report: https://oss-fuzz.com/testcase?key=5719392554450944 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdcff7da80 Crash State: clang::Sema::BuildCXXNestedNameSpecifier clang::Sema::IsInvalidUnlessNestedName clang::Parser::ParseOptionalCXXScopeSpecifier Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202006290157:202006300157 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5719392554450944 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
