[llvm-bugs] Issue 13826 in oss-fuzz: llvm/clang-fuzzer: Timeout in llvm_clang-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #8 on issue 13826 by ClusterFuzz-External: llvm/clang-fuzzer: Timeout in llvm_clang-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13826#c8 ClusterFuzz testcase 5092949752283136 appears to be flaky, updating reproducibility label. -- 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 11885 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #10 on issue 11885 by ClusterFuzz-External: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11885#c10 ClusterFuzz testcase 5096442061914112 appears to be flaky, updating reproducibility label. -- 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 12433 in oss-fuzz: llvm/llvm-itanium-demangle-fuzzer: Timeout in llvm_llvm-itanium-demangle-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #9 on issue 12433 by ClusterFuzz-External: llvm/llvm-itanium-demangle-fuzzer: Timeout in llvm_llvm-itanium-demangle-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12433#c9 ClusterFuzz testcase 6040956316418048 appears to be flaky, updating reproducibility label. -- 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 16890 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-01 Type: Bug New issue 16890 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16890 Detailed Report: https://oss-fuzz.com/testcase?key=5723531530207232 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff05cafd00 Crash State: processTypeAttrs ConvertDeclSpecToType GetDeclSpecTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201908280324:201908290314 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5723531530207232 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. -- 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] 5 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the reproducibility label flip to Unreproducible. This was an infrastructure issue that is now resolved. Switching the labels back, sorry for the inconvenience. Affected issues: issue 10821: llvm/clang-fuzzer: Stack-overflow in EvaluateValue http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10821 issue 11885: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11885 issue 12433: llvm/llvm-itanium-demangle-fuzzer: Timeout in llvm_llvm-itanium-demangle-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12433 issue 12439: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12439 issue 12898: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12898 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16889 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-01 Type: Bug New issue 16889 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16889 Detailed Report: https://oss-fuzz.com/testcase?key=5090109182967808 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd51d2eec8 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201908280324:201908290314 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5090109182967808 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. -- 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 43187] New: Crash given weak symbol in C, normal symbol in inline assembly
https://bugs.llvm.org/show_bug.cgi?id=43187
Bug ID: 43187
Summary: Crash given weak symbol in C, normal symbol in inline
assembly
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: jonathanchesterfi...@gmail.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com
For example,
__attribute__((weak)) int x = 4;
__asm__(".type x,@object\n"
".data\n"
".p2align 2\n"
"x:\n"
".long 42\n");
=> fatal error: error in backend: symbol 'x' is already defined
or, equivalently:
module asm ".type x,@object"
module asm ".data"
module asm ".p2align 2"
module asm "x:"
module asm ".long 42"
@x = weak dso_local global i32 4, align 4
=> same error
Expected behaviour is for x to have the initial value 42, replacing the weak
symbol. Observed behaviour is the fatal error.
Using non-inline assembly works as expected. Symbol overridden, no error.
Weak on either (or both) symbol(s) shows the same behaviour.
Non-reduced case has inline assembly in one translation unit and the weak
symbol in another. Compiling each separately to an elf and linking works fine,
llvm-link then llc fails as above.
--
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 43186] New: A list of clang-format options that don't work as documented/expected.
https://bugs.llvm.org/show_bug.cgi?id=43186 Bug ID: 43186 Summary: A list of clang-format options that don't work as documented/expected. Product: clang Version: 8.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: danielmruss...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org #The following options are in the online documentation but don't work at all # or are very defective in release (8.0.1). AllowAllConstructorInitializersOnNextLine: false BraceWrapping: AfterCaseLabel: true # AfterColon and BeforeColon fails to break at all BreakConstructorInitializers: AfterColon ConstructorInitializerAllOnOneLineOrOnePerLine: false # There appears to be no way to make sure clang will break # our constructor initializer lists. It REALLY wants to put them on the same # line. Also the options are a total mess right now, lacking symmetry. No one # online knows what the proper way to achieve this what they want w/ # constructor lists as a result. -- 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 43170] Crash test-suite/SingleSource/UnitTests/Vector/AVX512F/t_movzext.c
https://bugs.llvm.org/show_bug.cgi?id=43170 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||r370592 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Simon Pilgrim --- Fixed in rL370592 -- 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 16853 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Lexer::LexNumericConstant
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 16853 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Lexer::LexNumericConstant https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16853#c1 ClusterFuzz testcase 5741794200911872 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201908290314:201908310326 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 43185] New: Build fails using gn
https://bugs.llvm.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: Build fails using gn Product: Build scripts Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: cmake Assignee: unassignedb...@nondot.org Reporter: n@ndor.email CC: llvm-bugs@lists.llvm.org I am trying to add a new library under lib/clang/AST, along with a new tablegen backend. It seems like a bot is failing when trying to build with gn: http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-gn/builds/4816/steps/annotate/logs/stdio -- 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
