[llvm-bugs] [Bug 36737] --just-symbols file should count as an input
https://bugs.llvm.org/show_bug.cgi?id=36737 George Rimar changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from George Rimar --- Was fixed in r328852 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34948] -defsym should accept expressions, not just symbols
https://bugs.llvm.org/show_bug.cgi?id=34948 George Rimar changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from George Rimar --- We have this implemented. r317396. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35265] LLD produced executable with ld.bfd internal ldscript segfaults.
https://bugs.llvm.org/show_bug.cgi?id=35265 George Rimar changed: What|Removed |Added CC||gri...@accesssoftek.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from George Rimar --- This is already fixed (r319755+r318920+r318940). -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36974] New: segfault during bootstrap while building compiler-rt: comparison doesn't meet irreflexive requirements, assert(!(a < a)).
https://bugs.llvm.org/show_bug.cgi?id=36974
Bug ID: 36974
Summary: segfault during bootstrap while building compiler-rt:
comparison doesn't meet irreflexive requirements,
assert(!(a < a)).
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: matthias.krue...@famsik.de
CC: llvm-bugs@lists.llvm.org
Hi, this is my build script:
https://github.com/matthiaskrgr/llvm_bootstrap/blob/master/build_git.sh
There's a crash when building stage 3.
[ 96%/6101/6/6353,38805.436] Generating
SANITIZER_TEST_OBJECTS.sanitizer_procmaps_test.cc.x86_64.o
FAILED:
projects/compiler-rt/lib/sanitizer_common/tests/SANITIZER_TEST_OBJECTS.sanitizer_procmaps_test.cc.x86_64.o
cd
/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/projects/compiler-rt/lib/sanitizer_common/tests
&& /home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/./bin/clang -O3 -g0 -fPIC
-fvisibility-inlines-hidden -Werror=date-time
-Werror=unguarded-availability-new -std=c++11 -Wall -W -Wno-unused-parameter
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic
-Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor
-Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics
-ffunction-sections -fdata-sections -flto=full -Wall -std=c++11
-Wno-unused-parameter -Wno-unknown-warning-option -Wno-covered-switch-default
-DGTEST_NO_LLVM_RAW_OSTREAM=1 -DGTEST_HAS_RTTI=0
-I/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/utils/unittest/googletest/include
-I/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/utils/unittest/googletest
-I/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/projects/compiler-rt/include
-I/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/projects/compiler-rt/lib
-I/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/projects/compiler-rt/lib/sanitizer_common
-fno-rtti -O2 -Werror=sign-compare -Wno-non-virtual-dtor -gline-tables-only
-m64 -c -o SANITIZER_TEST_OBJECTS.sanitizer_procmaps_test.cc.x86_64.o
/home/matthias/LLVM/LLVM_dev/stage_3_tests/llvm/projects/compiler-rt/lib/sanitizer_common/tests/sanitizer_procmaps_test.cc
/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.1/../../../../include/c++/7.3.1/bits/stl_algo.h:5702:
Error: comparison doesn't meet irreflexive requirements, assert(!(a < a)).
Objects involved in the operation:
instance "functor" @ 0x0x7ffc8af39080 {
}
iterator::value_type "ordered type" {
}
#0 0x04666c19 PrintStackTraceSignalHandler(void*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x4666c19)
#1 0x04663c8a llvm::sys::RunSignalHandlers()
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x4663c8a)
#2 0x04664c48 SignalHandler(int)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x4664c48)
#3 0x7fbdd472bdd0 __restore_rt (/usr/lib/libpthread.so.0+0x11dd0)
#4 0x7fbdd321d860 __GI_raise (/usr/lib/libc.so.6+0x34860)
#5 0x7fbdd321eec9 __GI_abort (/usr/lib/libc.so.6+0x35ec9)
#6 0x7fbdd386deec get_max_length
/build/gcc/src/gcc/libstdc++-v3/src/c++11/debug.cc:551:0
#7 0x7fbdd386deec PrintContext
/build/gcc/src/gcc/libstdc++-v3/src/c++11/debug.cc:560:0
#8 0x7fbdd386deec __gnu_debug::_Error_formatter::_M_error() const
/build/gcc/src/gcc/libstdc++-v3/src/c++11/debug.cc:1015:0
#9 0x039844e3
llvm::ScalarEvolution::isKnownViaInduction(llvm::CmpInst::Predicate, llvm::SCEV
const*, llvm::SCEV const*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x39844e3)
#10 0x0398288a
llvm::ScalarEvolution::isKnownPredicate(llvm::CmpInst::Predicate, llvm::SCEV
const*, llvm::SCEV const*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x398288a)
#11 0x04775c57 (anonymous
namespace)::SimplifyIndvar::simplifyUsers(llvm::PHINode*, llvm::IVVisitor*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x4775c57)
#12 0x04774bb3 llvm::simplifyUsersOfIV(llvm::PHINode*,
llvm::ScalarEvolution*, llvm::DominatorTree*, llvm::LoopInfo*,
llvm::SmallVectorImpl&, llvm::SCEVExpander&,
llvm::IVVisitor*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x4774bb3)
#13 0x043da4ae (anonymous namespace)::IndVarSimplify::run(llvm::Loop*)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x43da4ae)
#14 0x043e76de (anonymous
namespace)::IndVarSimplifyLegacyPass::runOnLoop(llvm::Loop*,
llvm::LPPassManager&)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x43e76de)
#15 0x03909122 llvm::LPPassManager::runOnFunction(llvm::Function&)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x3909122)
#16 0x03f5625d llvm::FPPassManager::runOnFunction(llvm::Function&)
(/home/matthias/LLVM/LLVM_dev/stage_3_tests/objects/bin/clang-7+0x3f56
[llvm-bugs] [Bug 36554] Better error message for programs that need text relocations
https://bugs.llvm.org/show_bug.cgi?id=36554 George Rimar changed: What|Removed |Added CC||gri...@accesssoftek.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from George Rimar --- It was fixed in r327584 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36837] [AMDGPU][MC][GFX9] Missing instructions s_atomic_* and s_buffer_atomic_*
https://bugs.llvm.org/show_bug.cgi?id=36837 Dmitry changed: What|Removed |Added Fixed By Commit(s)||328975 Status|ASSIGNED|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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 7307 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_rotate: ASSERT: Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-04-02 Type: Bug New issue 7307 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_rotate: ASSERT: Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7307 Detailed report: https://oss-fuzz.com/testcase?key=5457660892676096 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_rotate Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_rotate Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!" llvm::AllocaInst::AllocaInst BitcodeReader::parseFunctionBody Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802210603:201802211531 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5457660892676096 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5020 in oss-fuzz: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits"
Updates: Labels: Deadline-Approaching Comment #3 on issue 5020 by sheriff...@chromium.org: llvm/clang-fuzzer: ASSERT: width && "Can't truncate to 0 bits" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5020#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5011 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Use-after-poison in DAGCombiner::useDivRem
Updates: Labels: Deadline-Approaching Comment #3 on issue 5011 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--x86_64-O2: Use-after-poison in DAGCombiner::useDivRem https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5011#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5044 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N->getNodeId() == -1 && "Node already inserted!"
Updates: Labels: Deadline-Approaching Comment #3 on issue 5044 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N->getNodeId() == -1 && "Node already inserted!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5044#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5035 in oss-fuzz: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record
Updates: Labels: Deadline-Approaching Comment #3 on issue 5035 by sheriff...@chromium.org: llvm/clang-fuzzer: ASSERT: CanDeclareSpecialMemberFunction(RD) && "doing special member lookup into record https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5035#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36976] New: [Formatter/ObjC] Formatter should not parse return type of ObjC method as cast
https://bugs.llvm.org/show_bug.cgi?id=36976
Bug ID: 36976
Summary: [Formatter/ObjC] Formatter should not parse return
type of ObjC method as cast
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: bhamilto...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
This bug is from the discussion at https://reviews.llvm.org/D44996 .
Currently, clang-format parses the r_paren in an ObjC method return type as
TT_CastRParen:
===
% echo "-(void)foo;" | ./bin/clang-format -debug -
Language: Objective-C
Line(0, FSC=0): minus[T=68, OC=0] l_paren[T=68, OC=1] void[T=68, OC=2]
r_paren[T=68, OC=6] identifier[T=68, OC=7] semi[T=68, OC=10]
Line(0, FSC=0): eof[T=68, OC=0]
Run 0...
AnnotatedTokens(L=0):
M=0 C=0 T=ObjCMethodSpecifier S=1 B=0 BK=0 P=0 Name=minus L=1 PPK=2
FakeLParens= FakeRParens=0 Text='-'
M=0 C=1 T=Unknown S=1 B=0 BK=0 P=33 Name=l_paren L=3 PPK=2
FakeLParens= FakeRParens=0 Text='('
M=0 C=1 T=Unknown S=0 B=0 BK=0 P=140 Name=void L=7 PPK=2 FakeLParens=
FakeRParens=0 Text='void'
M=0 C=0 T=CastRParen S=0 B=0 BK=0 P=43 Name=r_paren L=8 PPK=2
FakeLParens= FakeRParens=0 Text=')'
M=0 C=1 T=TrailingAnnotation S=0 B=0 BK=0 P=120 Name=identifier L=11
PPK=2 FakeLParens= FakeRParens=0 Text='foo'
M=0 C=0 T=Unknown S=0 B=0 BK=0 P=23 Name=semi L=12 PPK=2 FakeLParens=
FakeRParens=0 Text=';'
===
This seems unintentional; @djasper and I agreed we should revisit this.
There is at least one place which relies on TT_CastRParen being an indicator of
an ObjC method return type:
https://github.com/llvm-mirror/clang/blob/e37a191e99773959118155304ec2ed0bc0d591c2/lib/Format/TokenAnnotator.cpp#L394
so we will need to fix this carefully.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36704] [AMDGPU] Hang with gallium nine lighting shader likely caused by bad compilation
https://bugs.llvm.org/show_bug.cgi?id=36704 Axel Davy changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Axel Davy --- The bug was a mesa bug, not a llvm bug. More details on the mesa bug report. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36847] [AMDGPU][MC][GFX9] Missing instructions v_cvt_norm_*16_f16, v_sat_pk_u8_i16
https://bugs.llvm.org/show_bug.cgi?id=36847 Dmitry changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Fixed By Commit(s)||328988 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 10011] clang should warn on "string.empty()" when the return value is ignored
https://bugs.llvm.org/show_bug.cgi?id=10011 Marshall Clow (home) changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||mclow.li...@gmail.com --- Comment #11 from Marshall Clow (home) --- string.empty() is now marked "[[nodiscard]]" (after C++17) This was done as part of applying https://wg21.link/P600 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36042] [PCG] Redundant stack operations
https://bugs.llvm.org/show_bug.cgi?id=36042 Konstantin Belochapka changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #20 from Konstantin Belochapka --- Closing this one, as everybody agreed, no fix required. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36543] ArgumentPromotion optimization might break musttail invariants
https://bugs.llvm.org/show_bug.cgi?id=36543 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Reid Kleckner --- Fix landed in r326521, thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36546] GlobalOpt breaks musttail invariant
https://bugs.llvm.org/show_bug.cgi?id=36546 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||r...@google.com --- Comment #2 from Reid Kleckner --- Fix landed in r326376. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 27796] Calls to empty variadic functions in comdat no longer optimized out
https://bugs.llvm.org/show_bug.cgi?id=27796 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Reid Kleckner --- Really marking fixed in r321940. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36485] Crash when compiling LLVM IR with tons of musttail calls
https://bugs.llvm.org/show_bug.cgi?id=36485 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||r...@google.com --- Comment #6 from Reid Kleckner --- Fixed in r326404. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 27294] Dead argument elimination does not respect TCK_MustTail attribute
https://bugs.llvm.org/show_bug.cgi?id=27294 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED CC||r...@google.com Status|NEW |RESOLVED --- Comment #1 from Reid Kleckner --- This was fixed at some point in both DAE and ArgPromotion. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36977] New: [PPC64] V2 ABI: Implement symbol resolver stubs and set PPC64_GLINK dynamic tag
https://bugs.llvm.org/show_bug.cgi?id=36977 Bug ID: 36977 Summary: [PPC64] V2 ABI: Implement symbol resolver stubs and set PPC64_GLINK dynamic tag Product: lld Version: unspecified Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: sfert...@ca.ibm.com CC: llvm-bugs@lists.llvm.org The linker must provide a symbol resolver stub for each PLT entry. These resolver stubs are placed into a .glink section which is merged into the .text section of the executable/shared-object. The address of the resolver stubs is communicated to the dynamic linker by a DT_PPC64_GLINK tag in the dynamic section which has a d_ptr field set to 32 bytes before the first .glink resolver stub. Each resolver stub consists of a single instruction which branches to a common resolver entry point. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36978] New: ArrayRef defined in APInt.h
https://bugs.llvm.org/show_bug.cgi?id=36978 Bug ID: 36978 Summary: ArrayRef defined in APInt.h Product: Documentation Version: trunk Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: Doxygen Assignee: unassignedb...@nondot.org Reporter: tay...@hansenfamily.us CC: llvm-bugs@lists.llvm.org While looking at the Doxygen for ArrayRef, I was surprised to see that it says the class is defined in llvm/ADT/APInt.h at http://llvm.org/doxygen/APInt_8h_source.html#l00033. However, this looks like a declaration of the class, not a definition. Doxygen seems to be treating template declarations as definitions A solution for this would be to wrap template declarations in `/// \cond ... /// \endcond` doc comments which prevent Doxygen from creating documentation for it. Doing that fixes the issue for me. I'll assign myself to this bug. However, I suspect that other template classes are being affected by this as well, so we should look for them in other headers. It would also be nice to get some insight as to why Doxygen does this and how we can disable it. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36969] Different optimizations on similar code
https://bugs.llvm.org/show_bug.cgi?id=36969 Sanjay Patel changed: What|Removed |Added Fixed By Commit(s)||329011 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Sanjay Patel --- Should be fixed with: https://reviews.llvm.org/rL329011 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 7030 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain
Updates: Status: WontFix Comment #1 on issue 7030 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7030#c1 ClusterFuzz testcase 5422547328827392 is flaky and no longer crashes, so closing issue. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 31014] Clang crashes when optimizing code using notail call to a musttail function
https://bugs.llvm.org/show_bug.cgi?id=31014 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||ahata...@gmail.com --- Comment #4 from Reid Kleckner --- This should be fixed by r329015. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25641] clang-cl: vtordisp thunks not emitted for functions with class template specializations in their signatures
https://bugs.llvm.org/show_bug.cgi?id=25641 Reid Kleckner changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Reid Kleckner --- Should be fixed by r329009. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36287] String merging for symbol names
https://bugs.llvm.org/show_bug.cgi?id=36287 Rui Ueyama changed: What|Removed |Added Resolution|--- |WONTFIX Status|ASSIGNED|RESOLVED --- Comment #6 from Rui Ueyama --- Thank you for the numbers. I'm closing this bug as 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36979] New: [LLVM-COV] a return statement after a for statement is wrongly marked as executed
https://bugs.llvm.org/show_bug.cgi?id=36979
Bug ID: 36979
Summary: [LLVM-COV] a return statement after a for statement is
wrongly marked as executed
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: yangyib...@nju.edu.cn
CC: llvm-bugs@lists.llvm.org
$ clang -v
clang version 7.0.0- (trunk)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6.4.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.2.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.2.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8.0.0
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8.0.0
Candidate multilib: .;@m64
Selected multilib: .;@m64
$ cat small.c
int a = 1;
int main() {
for (; a < 9;)
return a;
return a;
}
$ clang -w -O0 -g -fcoverage-mapping -fprofile-instr-generate=small.profraw
small.c; ./a.out; llvm-profdata merge small.profraw -o small.profdata; llvm-cov
show a.out -instr-profile=small.profdata small.c > small.gcov; cat small.gcov
1| |int a = 1;
2| 1|int main() {
3| 1| for (; a < 9;)
4| 1|return a;
5| 1| return a;
6| 1|}
Line #5 is wrongly marked as executed.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36980] New: [LLVM-COV] The cond-expression and loop-expression of for statement in different lines lead to incorrect code coverage
https://bugs.llvm.org/show_bug.cgi?id=36980
Bug ID: 36980
Summary: [LLVM-COV] The cond-expression and loop-expression of
for statement in different lines lead to incorrect
code coverage
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: yangyib...@nju.edu.cn
CC: llvm-bugs@lists.llvm.org
$ clang -v
clang version 7.0.0- (trunk)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6.4.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/7.2.0
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.2.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8.0.0
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/8.0.0
Candidate multilib: .;@m64
Selected multilib: .;@m64
$ cat small.c
int a = 5;
void main ()
{
for (;
a < 4;
a = 7)
;
}
$ clang -w -O0 -g -fcoverage-mapping -fprofile-instr-generate=small.profraw
small.c; ./a.out; llvm-profdata merge small.profraw -o small.profdata; llvm-cov
show a.out -instr-profile=small.profdata small.c > small.gcov; cat small.gcov
1| |int a = 5;
2| |void main ()
3| 1|{
4| 1|for (;
5| 1| a < 4;
6| 1| a = 7)
7| 0|;
8| 1|}
Line #6 is wrongly marked as executed. However, the coverage information is
correct in gcov.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
