[llvm-bugs] [Bug 44257] For SHT_REL relocations, read addend from code or don't display it
https://bugs.llvm.org/show_bug.cgi?id=44257 George Rimar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from George Rimar --- Fixed in 98a4289810ba49cea6f9a9be6d902e72f0c0d0e7 -- 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 48501] New: Clang emits __attribute__((__used__)) functions in submodules that weren't imported
https://bugs.llvm.org/show_bug.cgi?id=48501
Bug ID: 48501
Summary: Clang emits __attribute__((__used__)) functions in
submodules that weren't imported
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Modules
Assignee: unassignedclangb...@nondot.org
Reporter: teempe...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
The example below reproduces the bug. 'use.h' is never actually imported by
main.cpp, but as it's in the same top-level module as 'other.h', the
'call_undefined' function is still deserialised and emitted. Note that this
happens with local-submodule-visibility turned on and off (at least with LSV=on
this seems like a bug):
$ cat main.cpp
#include "other.h"
int main() {}
$ cat other.h
struct Foo {
};
$ cat use.h
int undefined();
__attribute__((__used__))
inline int call_undefined() { undefined(); }
$ cat module.modulemap
module A {
module Use { header "use.h" export * }
module Other { header "other.h" export * }
}
$ clang main.cpp -fmodules -fcxx-modules -Rmodule-build
-fmodules-cache-path=pcms -Xclang -fmodules-local-submodule-visibility
Undefined symbols for architecture x86_64:
"undefined()", referenced from:
call_undefined() in main-fe42f9.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
$ clang main.cpp -fmodules -fcxx-modules -Rmodule-build
-fmodules-cache-path=pcms -Xclang -fmodules-local-submodule-visibility -S
-emit-llvm -o - | grep undefined
@llvm.used = appending global [1 x i8*] [i8* bitcast (i32 ()*
@_Z14call_undefinedv to i8*)], section "llvm.metadata"
define linkonce_odr i32 @_Z14call_undefinedv() #0 {
%2 = call i32 @_Z9undefinedv()
declare i32 @_Z9undefinedv() #1
--
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 39709] [X86] Suboptimal code in vXi8 vector multiply reduction
https://bugs.llvm.org/show_bug.cgi?id=39709 Simon Pilgrim changed: What|Removed |Added Status|CONFIRMED |RESOLVED Fixed By Commit(s)||47321c311bdbe0145b9bf45d822 ||185c37b19fa50 Resolution|--- |FIXED --- Comment #3 from Simon Pilgrim --- Fixed in rG47321c311bdbe0145b9bf45d822185c37b19fa50 - we were able to get quite close with SimplifyDemandedBits/SimplifyDemandedVectorElts + shuffle combining but just a custom promotion to a vXi16 reduction worked best in the end. -- 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 48051] [OssFuzz Issue 26832] "No point in having a non-constant max backedge taken count!"
https://bugs.llvm.org/show_bug.cgi?id=48051 Simon Pilgrim changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Pilgrim --- OSS Fuzz reports this was fixed in the range: https://github.com/llvm/llvm-project/compare/4a771108ac5ceeae6119185ae52ab6f5e6af2da1...6ef07111a402a87fda096b6b8d7327e4aa89d4d6 I added a test case at: 5a02bf4f950e -- 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 28659 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !hasVectorValue(Key, Part) && "Vector value already set for part"
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-12-14 Type: Bug New issue 28659 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !hasVectorValue(Key, Part) && "Vector value already set for part" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28659 Detailed Report: https://oss-fuzz.com/testcase?key=5139644983410688 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !hasVectorValue(Key, Part) && "Vector value already set for part" llvm::VectorizerValueMap::setVectorValue llvm::InnerLoopVectorizer::widenInstruction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012120615:202012130615 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5139644983410688 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 28650 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 28650 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28650#c1 ClusterFuzz testcase 4914352473899008 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012130615:202012140607 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 48502] New: JITLink.cpp doens't build with msvc, xcode clang, gcc
https://bugs.llvm.org/show_bug.cgi?id=48502 Bug ID: 48502 Summary: JITLink.cpp doens't build with msvc, xcode clang, gcc Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: MCJIT Assignee: unassignedb...@nondot.org Reporter: nicolaswe...@gmx.de CC: 1101.deb...@gmail.com, llvm-bugs@lists.llvm.org linux: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8860956485677512080/+/steps/package_clang/0/stdout?format=raw mac: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8860956485677512064/+/steps/package_clang/0/stdout?format=raw win: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8860956485677512048/+/steps/package_clang/0/stdout?format=raw The diagnostics are a bit hard to understand. Maybe it complains that llvm::jitlink::LinkGraph::nested_collection_iterator<> doesn't have an operator!=. Not 100% sure which of the changes yesterday triggered this. 04795ab8368a9f4169b737e6db2aebea47d6cf10 is the only one to touch JITLink.h recently, but that might not be it. (Would've been nice to have a phab link in the commit message so that I could've mentioned this there.) -- 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 28436 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::Sema::getTypeName
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 28436 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::Sema::getTypeName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28436#c1 ClusterFuzz testcase 5675986431639552 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012130615:202012140607 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 48503] New: clangd not able to navigate from declaration to implementation
https://bugs.llvm.org/show_bug.cgi?id=48503 Bug ID: 48503 Summary: clangd not able to navigate from declaration to implementation Product: clang-tools-extra Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: clangd Assignee: unassignedclangb...@nondot.org Reporter: leona...@adacore.com CC: llvm-bugs@lists.llvm.org Created attachment 24281 --> https://bugs.llvm.org/attachment.cgi?id=24281&action=edit Sources showing the mentioned bug Hello, The textDocument/definition request is failing on the functions declared in hi.h: executing the request on these declarations end up with an empty response. Interestingly, the same request works fine on the implementations of these functions, present in the hi.c file. I have attached the reproducer, with the compile_commands.json file used (which looks perfectly good to me). -- 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 #4 on issue 27686 by ClusterFuzz-External: llvm: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27686#c4 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-56a2eda4-be7c-435a-97cd-2e54f2ac5190.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 48485] LLVM11: LLD Source code on llvm.org points to a very outdated package (pre llvm11-rc1)
https://bugs.llvm.org/show_bug.cgi?id=48485 Laurentiu Tertan changed: What|Removed |Added Resolution|--- |INVALID 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 48504] New: ColumnLimit with inline comments
https://bugs.llvm.org/show_bug.cgi?id=48504 Bug ID: 48504 Summary: ColumnLimit with inline comments Product: clang Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: ckra...@ara.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org We would appreciate an option in clang-format to not count inline comments against a line's column limit. std::string test = "this is a string"; // and has an inline comment ^ last "actual" character to count So assuming the new option was something like IncludeInlineCommentsInColumLimit, if true follow the ReflowComments option, if false leave the comment alone unless the actual code itself exceeds the column limit. -- 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 48505] New: PCH use over-aggressively validates input header mtime
https://bugs.llvm.org/show_bug.cgi?id=48505 Bug ID: 48505 Summary: PCH use over-aggressively validates input header mtime Product: clang Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: daniel.johns...@intel.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Problem: Build system has sporadic build failures with errors similar to this: fatal error: file '/usr/include/linux/stddef.h' has been modified since the precompiled header '' was built: mtime changed note: please rebuild precompiled header '' In my case, this occurs when Ubuntu decides to update a package that includes the /usr/include/linux/stddef.h file automatically due to a security fix. However, since the OS package being deployed was built before the last PCH file build, most build systems don't retrigger a PCH file build. When using the PCH (due to other build dependency changes), clang will fail because the mtime was updated (even if the mtime is older than the PCH file). I'm guessing I could use -fno-validate-pch to work around this issue, however, I can't seem to find sufficient documentation of that option to determine if this would work or what other (desirable) checks would be disabled. In short: build systems typically only check that the mtime of dependent files are not newer than the target file clang fails when dependent file mtime was updated since pch creation, but is not newer than the actual pch file. -- 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 48506] New: Crash during emmake of module that used to build in 2.0.8 --(2.0.10 and 2.0.9), 2.0.8 works)
https://bugs.llvm.org/show_bug.cgi?id=48506 Bug ID: 48506 Summary: Crash during emmake of module that used to build in 2.0.8 --(2.0.10 and 2.0.9), 2.0.8 works) Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: wasm Assignee: unassignedb...@nondot.org Reporter: mark.d...@siemens.com CC: llvm-bugs@lists.llvm.org, s...@chromium.org built on windows 10 in Ubuntu Linux shell. unexpected relocation type UNREACHABLE executed at /b/s/w/ir/cache/builder/emscripten-releases/llvm-project/lld/wasm/InputFiles.cpp:131! PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: /mnt/d/Git/emsdk/upstream/bin/wasm-ld -o /mnt/d/Git/sessionservicejs/dmuservices/png/../lib/libsiemenspng.so /mnt/d/Git/sessionservicejs/dmuservices/png/Release/png.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngerror.o -L/mnt/d/Git/emsdk/upstream/emscripten/system/local/lib /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngget.o -L/mnt/d/Git/emsdk/upstream/emscripten/system/lib /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngmem.o -L/mnt/d/Git/emsdk/upstream/emscripten/cache/wasm /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngpread.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngread.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngrio.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngrtran.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngrutil.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngset.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngtrans.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngwio.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngwrite.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngwtran.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngwutil.o -L/mnt/d/Git/sessionservicejs/dmuservices/png/../lib --relocatable -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr #0 0x7f3ba1f5add3 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/mnt/d/Git/emsdk/upstream/bin/../lib/libLLVM-12git.so+0x86bdd3) #1 0x7f3ba1f58b2e llvm::sys::RunSignalHandlers() (/mnt/d/Git/emsdk/upstream/bin/../lib/libLLVM-12git.so+0x869b2e) #2 0x7f3ba1f5b295 SignalHandler(int) (/mnt/d/Git/emsdk/upstream/bin/../lib/libLLVM-12git.so+0x86c295) #3 0x7f3ba57f83c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x153c0) #4 0x7f3ba13c618b raise (/lib/x86_64-linux-gnu/libc.so.6+0x4618b) #5 0x7f3ba13a5859 abort (/lib/x86_64-linux-gnu/libc.so.6+0x25859) #6 0x7f3ba1ea5511 (/mnt/d/Git/emsdk/upstream/bin/../lib/libLLVM-12git.so+0x7b6511) #7 0x0079292d lld::wasm::ObjFile::calcNewAddend(llvm::wasm::WasmRelocation const&) const (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x79292d) #8 0x0078fed9 lld::wasm::InputChunk::writeRelocations(llvm::raw_ostream&) const (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x78fed9) #9 0x007c2c6c lld::wasm::CodeSection::writeRelocations(llvm::raw_ostream&) const (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x7c2c6c) #10 0x007ca099 lld::wasm::RelocSection::writeBody() (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x7ca099) #11 0x007b691a lld::wasm::SyntheticSection::finalizeContents() (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x7b691a) #12 0x007b0778 lld::wasm::(anonymous namespace)::Writer::run() (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x7b0778) #13 0x007a8941 lld::wasm::writeResult() (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x7a8941) #14 0x0078b362 lld::wasm::(anonymous namespace)::LinkerDriver::link(llvm::ArrayRef) (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x78b362) #15 0x00784b53 lld::wasm::link(llvm::ArrayRef, bool, llvm::raw_ostream&, llvm::raw_ostream&) (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x784b53) #16 0x0048ac1d lldMain(int, char const**, llvm::raw_ostream&, llvm::raw_ostream&, bool) (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x48ac1d) #17 0x0048a740 main (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x48a740) #18 0x7f3ba13a70b3 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b3) #19 0x0048a41a _start (/mnt/d/Git/emsdk/upstream/bin/wasm-ld+0x48a41a) emcc: error: '/mnt/d/Git/emsdk/upstream/bin/wasm-ld -o /mnt/d/Git/sessionservicejs/dmuservices/png/../lib/libsiemenspng.so /mnt/d/Git/sessionservicejs/dmuservices/png/Release/png.o /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngerror.o -L/mnt/d/Git/emsdk/upstream/emscripten/system/local/lib /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngget.o -L/mnt/d/Git/emsdk/upstream/emscripten/system/lib /mnt/d/Git/sessionservicejs/dmuservices/png/Release/pngmem.o -L/mnt/d/Git/emsdk/upstream/emscripten/cache/wasm /mnt/d/Git/sess
[llvm-bugs] [Bug 48502] JITLink.cpp doens't build with msvc, xcode clang, gcc
https://bugs.llvm.org/show_bug.cgi?id=48502 Nico Weber changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Nico Weber --- ...yup, https://reviews.llvm.org/D91488#2451534 Sorry about the incorrect attribution, Lang! -- 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 24113] Assertion: "Insufficient alignment"=" in IntervalMap.h:1045 in 32-bit MSVC builds
https://bugs.llvm.org/show_bug.cgi?id=24113 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Reid Kleckner --- This is stale. We ultimately did put the alignas on the IntervalMap, and then we removed it, and maybe now we need it again. See: https://reviews.llvm.org/D92509 -- 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 48451] clang fails to build llvm-11.0.0 in 32-bit mode when XOP instructions are enabled
https://bugs.llvm.org/show_bug.cgi?id=48451 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Fixed By Commit(s)|57c0c4a27575840ae0a48eb9f84 |57c0c4a27575840ae0a48eb9f84 |55a5ed087c857 |55a5ed087c857 ca8de9ad8895 --- Comment #8 from Tom Stellard --- Merged: ca8de9ad8895 -- 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 48451, which changed state. Bug 48451 Summary: clang fails to build llvm-11.0.0 in 32-bit mode when XOP instructions are enabled https://bugs.llvm.org/show_bug.cgi?id=48451 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48157] Please merge cffb0dd54d41d8e249d2009467c4beb5b681ba26 into 11.0.1 [SemaTemplate] Stop passing insertion position around during VarTemplate instantiation
https://bugs.llvm.org/show_bug.cgi?id=48157 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|cffb0dd54d41d8e249d2009467c |cffb0dd54d41d8e249d2009467c |4beb5b681ba26 |4beb5b681ba26 fc23bc9b30bf --- Comment #6 from Tom Stellard --- Merged: fc23bc9b30bf -- 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 48157, which changed state. Bug 48157 Summary: Please merge cffb0dd54d41d8e249d2009467c4beb5b681ba26 into 11.0.1 [SemaTemplate] Stop passing insertion position around during VarTemplate instantiation https://bugs.llvm.org/show_bug.cgi?id=48157 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 48390] [InstCombine] Miscompile, improper substitution of uadd.sat
https://bugs.llvm.org/show_bug.cgi?id=48390 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|f16320b90b8381f2e3aac1ec17f |f16320b90b8381f2e3aac1ec17f |39eff06f09ea0 |39eff06f09ea0 |e6f2a79d7aa01f8dd7f0194f97a |e6f2a79d7aa01f8dd7f0194f97a |50b480e8ede71 |50b480e8ede71 934376da5851 ||8511a8df838f Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Tom Stellard --- Merged: 8511a8df838f -- 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 48390, which changed state. Bug 48390 Summary: [InstCombine] Miscompile, improper substitution of uadd.sat https://bugs.llvm.org/show_bug.cgi?id=48390 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 48492] Please pick c28b18af19621e6b5cca257ef7139ba93833df0c to release/11.x
https://bugs.llvm.org/show_bug.cgi?id=48492 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|c28b18af19621e6b5cca257ef71 |c28b18af19621e6b5cca257ef71 |39ba93833df0c |39ba93833df0c 861b2a24bc49 Status|NEW |RESOLVED --- Comment #4 from Tom Stellard --- Merged: 861b2a24bc49 -- 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 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 48492, which changed state. Bug 48492 Summary: Please pick c28b18af19621e6b5cca257ef7139ba93833df0c to release/11.x https://bugs.llvm.org/show_bug.cgi?id=48492 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48492, which changed state. Bug 48492 Summary: Please pick c28b18af19621e6b5cca257ef7139ba93833df0c to release/11.x https://bugs.llvm.org/show_bug.cgi?id=48492 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 48404] Missed Optimization: CLZ Loop -> CLZ instruction
https://bugs.llvm.org/show_bug.cgi?id=48404 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||25067f179f33ba1b764ac7a7d83 ||385c8fd73801f --- Comment #2 from Craig Topper --- We should recognize this loop after 25067f179f33ba1b764ac7a7d83385c8fd73801f -- 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 48507] New: Type traits error in c++17 version
https://bugs.llvm.org/show_bug.cgi?id=48507 Bug ID: 48507 Summary: Type traits error in c++17 version Product: libc++ Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: krylov.yaros...@gmail.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Here is the two strings code using type traits: ``` #include "nlohmann/json.hpp" static_assert( std::is_copy_assignable::value, "" ); ``` https://godbolt.org/z/4eqjas It works perfectly with libstdc++, and it works with libc++ using c++11 or c++14. But libc++ with c++17 can't compile this code. I tried to dig into problem, to find the difference between c++17 and non-c++17 in libc++ headers, I tried to dig into nlohmann json to extract minimal example, but failed. Root issue on Github: https://github.com/nlohmann/json/issues/2491 -- 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 48201, which changed state. Bug 48201 Summary: [LLVM 11 regression] MC assembler check, rejects common assembler code as, e.g., generated by GCC https://bugs.llvm.org/show_bug.cgi?id=48201 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 48201] [LLVM 11 regression] MC assembler check, rejects common assembler code as, e.g., generated by GCC
https://bugs.llvm.org/show_bug.cgi?id=48201 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)|1deff4009e0ae661b03682901bf |1deff4009e0ae661b03682901bf |6932297ce7ea1 |6932297ce7ea1 700baa009dc6 --- Comment #4 from Tom Stellard --- Merged: 700baa009dc6 -- 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 48508] New: Failure to optimize code converted to memset call into tail call
https://bugs.llvm.org/show_bug.cgi?id=48508
Bug ID: 48508
Summary: Failure to optimize code converted to memset call into
tail call
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: gabrav...@gmail.com
CC: llvm-bugs@lists.llvm.org
void f(char *d, size_t c)
{
while (c-- > 0)
*d++ = 0;
}
This code can be optimized to using `memset`. It can also be further optimize
to optimize out the call to `memset` to a tail call. This transformation is
done by GCC, but not by LLVM.
Comparison here : https://godbolt.org/z/sjP8P8
--
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 48428] x32: support variadic functions
https://bugs.llvm.org/show_bug.cgi?id=48428 Harald van Dijk changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||9eac818370fe4b50a167627593b ||fe53e61c216bc --- Comment #1 from Harald van Dijk --- Fixed by D93160. -- 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 28673 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::ASTContext::getTypeInfo
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-12-15 Type: Bug New issue 28673 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::ASTContext::getTypeInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28673 Detailed Report: https://oss-fuzz.com/testcase?key=5681870947876864 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc43363fc0 Crash State: clang::ASTContext::getTypeInfo clang::ASTContext::getIntWidth IntExprEvaluator::Success Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012130615:202012140607 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5681870947876864 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 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48431, which changed state. Bug 48431 Summary: Cherry pick 1c98f984105e to the 11 release branch. https://bugs.llvm.org/show_bug.cgi?id=48431 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 48431] Cherry pick 1c98f984105e to the 11 release branch.
https://bugs.llvm.org/show_bug.cgi?id=48431 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|1c98f984105e|1c98f984105e 200eb1abe2a1 --- Comment #8 from Tom Stellard --- Merged: 200eb1abe2a1 -- 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 45410] Assertion `getOperand(0)->getType() == cast(getOperand(1)->getType())->getElementType() && "Ptr must be a pointer to Val type!"' failed
https://bugs.llvm.org/show_bug.cgi?id=45410 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|e09107ab80dced55414fa458cf7 |e09107ab80dced55414fa458cf7 |8e6cdfe90da6e |8e6cdfe90da6e |a1aa330b202f97ecd243ea9ef0c |a1aa330b202f97ecd243ea9ef0c |7ac00a80ea653 |7ac00a80ea653 |1c604a9f5fd65c91f097c856fa6 |1c604a9f5fd65c91f097c856fa6 |643373fc869e1 8fb2a235b0f2 |643373fc869e1 8fb2a235b0f2 ||98f575ff55bff1e4128ffaeef4d ||05c356d996ab9 ||0312bec0d7573b0549a222fb5d0 ||a695fcf819dc3 ||fdab756331f322a9818c1bdf14d ||23d9cd6036 Status|CONFIRMED |RESOLVED --- Comment #18 from Tom Stellard --- Merged: 98f575ff55bff1e4128ffaeef4d05c356d996ab9 0312bec0d7573b0549a222fb5d0a695fcf819dc3 fdab756331f322a9818c1bdf14d23d9cd6036c81 adf845300c9cc023d386d97b6ebeb1e82bd97763 -- 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 45410, which changed state. Bug 45410 Summary: Assertion `getOperand(0)->getType() == cast(getOperand(1)->getType())->getElementType() && "Ptr must be a pointer to Val type!"' failed https://bugs.llvm.org/show_bug.cgi?id=45410 What|Removed |Added Status|CONFIRMED |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 48509] New: Fail to parse empty target region
https://bugs.llvm.org/show_bug.cgi?id=48509 Bug ID: 48509 Summary: Fail to parse empty target region Product: OpenMP Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Clang Compiler Support Assignee: unassignedclangb...@nondot.org Reporter: jonathanchesterfi...@gmail.com CC: llvm-bugs@lists.llvm.org #pragma omp declare target #pragma omp end declare target > error: expected '#pragma omp end declare target' https://godbolt.org/z/W4rbca Putting int x; between the pragmas is sufficient to resolve this. Fails on trunk, nvptx as well as older compilers. -- 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 48510] New: Safestack option crashes when used on 32-bit builds
https://bugs.llvm.org/show_bug.cgi?id=48510
Bug ID: 48510
Summary: Safestack option crashes when used on 32-bit builds
Product: compiler-rt
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: compiler-rt
Assignee: unassignedb...@nondot.org
Reporter: shrava...@gmail.com
CC: llvm-bugs@lists.llvm.org
I am attempting to use the safe-stack feature `-fsanitize=safe-stack` with
clang-11. I tested a simple hello world program in 32-bit compilation an Ubuntu
64 machine, however the program when run crashes with the error message
```
safestack CHECK failed:
/build/llvm-toolchain-11-11.0.0~++20200929060912+dda0a1867cc/compiler-rt/lib/safestack/safestack.cpp:95
MAP_FAILED != addr
Aborted (core dumped)
```
I wanted to check if SafeStack is indeed supported in 32-bit compilations?
If so, any help debugging this would be very helpful.
For completeness, here is the compilation command
```
clang-11 -m32 -g -O0 -fsanitize=safe-stack ./helloworld.c -o ./helloworld &&
./helloworld
```
And here is the program being compiled.
```
#include
int main(int argc, char const *argv[])
{
printf("Hello World\n");
return 0;
}
```
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34581] LLVM miscompiles calls to "operator delete" under -Oz
https://bugs.llvm.org/show_bug.cgi?id=34581 James Y Knight changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||jykni...@google.com Resolution|--- |FIXED --- Comment #18 from James Y Knight --- Sounds like this is fixed with the commit from the last comment. -- 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 48511] New: ld64.lld.darwinnew linked v8_context_snapshot_generator doesn't run on macos 10.15.7 (and possibly other macos versions)
https://bugs.llvm.org/show_bug.cgi?id=48511 Bug ID: 48511 Summary: ld64.lld.darwinnew linked v8_context_snapshot_generator doesn't run on macos 10.15.7 (and possibly other macos versions) Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: MachO Assignee: unassignedb...@nondot.org Reporter: nicolaswe...@gmx.de CC: llvm-bugs@lists.llvm.org repro file here https://drive.google.com/file/d/1yKoVlb8e7A_AjaRad2fdiQRpo_7xJK7T/view?usp=sharing (uses thin static archives, so regular ld can't link it. I can make a normal repro if it's useful) % ./v8_context_snapshot_generator dyld: Symbol not found: _kCGColorSpaceITUR_2100_HLG Referenced from: /Users/thakis/src/chrome/src/out/gn/./v8_context_snapshot_generator Expected in: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices in /Users/thakis/src/chrome/src/out/gn/./v8_context_snapshot_generator zsh: abort ./v8_context_snapshot_generator It should probably pick up the def from CoreGraphics instead -- it's maybe similar to bug 48395. However, CoreGraphics used to be in ApplicationServices, and ApplicationServices.tbd has these magic symbols: symbols: [ '$ld$install_name$os10.4$/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices', '$ld$install_name$os10.5$/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices', '$ld$install_name$os10.6$/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices', '$ld$install_name$os10.7$/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices', 10.7 is maybe old enough that we don't _have_ to handle these magic symbols, but we might encounter them in a separate context. But it's probably off topic for this bug. -- 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 48512] New: [arm assembler]: Incorrect ARM alignment NOPs in mixed ARM and Thumb assembly
https://bugs.llvm.org/show_bug.cgi?id=48512 Bug ID: 48512 Summary: [arm assembler]: Incorrect ARM alignment NOPs in mixed ARM and Thumb assembly Product: libraries Version: 10.0 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: Backend: ARM Assignee: unassignedb...@nondot.org Reporter: husseyde...@gmail.com CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com, ties.st...@arm.com Seems to be related to bug 18019. In a mixed ARM and Thumb file, two Thumb NOPs will be emitted in a manual alignment, even in ARM mode. This rarely causes an issue in practice, as most uses of 8-byte alignment are for constant pools which will be branched over anyways, but it is an issue nonetheless. .syntax unified .text .globl arm .type arm, %function .p2align 3, 0 @ 8-byte align arm: nop @ normal nop, now we are not 8-byte aligned .p2align 3, 0 @ align again bx lr .thumb @ we just need this directive in the file to trigger the bug, no Thumb code is required $ clang --target=arm-none-eabi -march=armv4t -c test.s -o test.o $ arm-none-eabi-objdump -d test.o test.o: file format elf32-littlearm Disassembly of section .text: : 0: e1a0nop ; (mov r0, r0) 4: 46c046c0strbmi r4, [r0], r0, asr #13 8: e12fff1ebx lr While the manual nop is correct, the implicit alignment nop is two Thumb nops. -- 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 48270] Backport ccba60a784e7 to 11.0
https://bugs.llvm.org/show_bug.cgi?id=48270 Valentin Churavy changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #5 from Valentin Churavy --- Sorry didn't have time to work on this. Okay to skip. -- 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 48270, which changed state. Bug 48270 Summary: Backport ccba60a784e7 to 11.0 https://bugs.llvm.org/show_bug.cgi?id=48270 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- 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 48222] Default argument of constexpr functions not usable in template using?
https://bugs.llvm.org/show_bug.cgi?id=48222 Faisal Vali changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID CC||fais...@yahoo.com --- Comment #1 from Faisal Vali --- We discussed this bug on the core reflector - and Richard Smith made the case that clang's behavior here was justified per the current wording http://eel.is/c++draft/temp.res.general#8 (though, reportedly, the resolution of core issue 2335 might still alter the expectation here). So, apparently (to my surprise too) this has not been deemed a bug - and I am marking it as such. Please feel free to reopen the issue if you still feel (and can make the case) - based on wording from the standard - that we've missed something - and that this is indeed a bug. Thank you for taking the time to submit this 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] Issue 28678 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup
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-12-15 Type: Bug New issue 28678 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28678 Detailed Report: https://oss-fuzz.com/testcase?key=5374165783805952 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff72387a88 Crash State: clang::DeclContext::lookup clang::DeclContext::using_directives UnqualUsingDirectiveSet::addUsingDirectives Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011130615:202011140605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5374165783805952 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
