[llvm-bugs] Issue 10287 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?"
Comment #2 on issue 10287 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10287#c2 ClusterFuzz has detected this issue as fixed in range 201809100126:201809110126. Detailed report: https://oss-fuzz.com/testcase?key=5131837354016768 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-earlycse Fuzz target binary: llvm-opt-fuzzer--x86_64-earlycse Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !FoundVal && "Key already in new map?" llvm::DenseMapBasellvm::ScopedHashTableVal llvm::DenseMapBasellvm::ScopedHashTableVal Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201809070126:201809080127 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201809100126:201809110126 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5131837354016768 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- 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 10287 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 10287 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10287#c3 ClusterFuzz testcase 5131837354016768 is verified as fixed, so closing issue as verified. 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 37253] Coalescer segfault
https://bugs.llvm.org/show_bug.cgi?id=37253 Bevin Hansson changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Bevin Hansson --- The reduced reproducer (and the original as well) no longer cause this issue. The code hasn't changed, so something else has caused it to no longer exhibit the crash. Closing this ticket. -- 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 31095] During loop-deletion: Assertion `use_empty() && "Uses remain when a value is destroyed!"' failed.
https://bugs.llvm.org/show_bug.cgi?id=31095 bjorn.a.petters...@ericsson.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||rL322357 --- Comment #1 from bjorn.a.petters...@ericsson.com --- Can't reproduce this any longer. Problem was solved by rL322357: Author: Serguei Katkov Date: Fri Jan 12 07:24:43 2018 + [LoopDeletion] Handle users in unreachable block This is a fix for PR35884. When we want to delete dead loop we must clean uses in unreachable blocks otherwise we'll get an assert during deletion of instructions from the loop. Reviewers: anna, davide Reviewed By: anna Subscribers: llvm-commits, lebedev.ri Differential Revision: https://reviews.llvm.org/D41943 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@322357 91177308-0d34-0410-b5e6-96231b3b80d8 -- 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 38900] New: random_shuffle swaps elements with themselves
https://bugs.llvm.org/show_bug.cgi?id=38900 Bug ID: 38900 Summary: random_shuffle swaps elements with themselves Product: libc++ Version: 7.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: tdh...@gmail.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com The version of std::random_shuffle() that takes a custom PRNG can call swap(a, a) (i.e. swap an element with itself. I'd say that should be fine according to the standard but in practice some things don't like this (in my cast Boost's small_vector) and so you randomly get assertion failures which is rather annoying (I will submit a patch to Boost for this too). Anyway this should definitely be fixed - this bug existed in old versions of libstdc++ but they fixed it. And more importantly the other versions of std::random_shuffle, and std::shuffle have been fixed. The fix is simple, just add if (__i != difference_type(0)) Here: https://github.com/llvm-mirror/libcxx/blob/ed6c20e48d547bdda5c68ba1b8f79a16916683ab/include/algorithm#L2989 I would do a pull request but it looks like you are still using SVN... -- 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 38861] Emit third operand for the rdhwr instruction on MIPS64 < R6
https://bugs.llvm.org/show_bug.cgi?id=38861 Simon Atanasyan changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Simon Atanasyan --- Fixed at r341919. https://reviews.llvm.org/rL341919 -- 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 38383] Missing negation in if statement, error message will be ignored
https://bugs.llvm.org/show_bug.cgi?id=38383 Raphael Isemann changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||r341940 Status|ASSIGNED|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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38901] New: compiler-rt 7.0.0rc3 regressions: TestCases/Linux/fork_and_leak.cc
https://bugs.llvm.org/show_bug.cgi?id=38901 Bug ID: 38901 Summary: compiler-rt 7.0.0rc3 regressions: TestCases/Linux/fork_and_leak.cc Product: compiler-rt Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: compiler-rt Assignee: unassignedb...@nondot.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org Blocks: 38406 Failing Tests (2): LeakSanitizer-AddressSanitizer-i386 :: TestCases/Linux/fork_and_leak.cc LeakSanitizer-Standalone-i386 :: TestCases/Linux/fork_and_leak.cc FAIL: LeakSanitizer-AddressSanitizer-i386 :: TestCases/Linux/fork_and_leak.cc (2698 of 5721) TEST 'LeakSanitizer-AddressSanitizer-i386 :: TestCases/Linux/fork_and_leak.cc' FAILED Script: -- : 'RUN: at line 2'; /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/lib/llvm/7/bin/clang --driver-mode=g++ -O0 -m32 -gline-tables-only -fsanitize=address -I/var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/../ /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -o /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386AsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp && not /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386AsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp 2>&1 | FileCheck /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -- Exit Code: 2 Command Output (stderr): -- + : 'RUN: at line 2' + /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/lib/llvm/7/bin/clang --driver-mode=g++ -O0 -m32 -gline-tables-only -fsanitize=address -I/var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/../ /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -o /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386AsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp + FileCheck /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc + not /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386AsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp FileCheck error: '-' is empty. FileCheck command line: FileCheck /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -- FAIL: LeakSanitizer-Standalone-i386 :: TestCases/Linux/fork_and_leak.cc (2780 of 5721) TEST 'LeakSanitizer-Standalone-i386 :: TestCases/Linux/fork_and_leak.cc' FAILED Script: -- : 'RUN: at line 2'; /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/lib/llvm/7/bin/clang --driver-mode=g++ -O0 -m32 -gline-tables-only -fsanitize=leak -I/var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/../ /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -o /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386LsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp && not /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386LsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp 2>&1 | FileCheck /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -- Exit Code: 2 Command Output (stderr): -- + : 'RUN: at line 2' + /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/lib/llvm/7/bin/clang --driver-mode=g++ -O0 -m32 -gline-tables-only -fsanitize=leak -I/var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/../ /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-7.0.0rc3.src/test/lsan/TestCases/Linux/fork_and_leak.cc -o /var/tmp/portage/sys-libs/compiler-rt-sanitizers-7.0.0_rc3/work/compiler-rt-sanitizers-7.0.0_rc3_build/test/lsan/I386LsanConfig/TestCases/Linux/Output/fork_and_leak.cc.tmp + not /var/tmp/portage/sys-libs/co
[llvm-bugs] [Bug 37962] [debugify] callsite-splitting fail
https://bugs.llvm.org/show_bug.cgi?id=37962 Florian Hahn changed: What|Removed |Added Fixed By Commit(s)||341970 Resolution|--- |FIXED 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37953] [meta] [debugify] fix -check-debugify failures
https://bugs.llvm.org/show_bug.cgi?id=37953 Bug 37953 depends on bug 37962, which changed state. Bug 37962 Summary: [debugify] callsite-splitting fail https://bugs.llvm.org/show_bug.cgi?id=37962 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38900] random_shuffle swaps elements with themselves
https://bugs.llvm.org/show_bug.cgi?id=38900 Marshall Clow (home) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Marshall Clow (home) --- Fixed in revision 341975. -- 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 38902] New: incorrect diagnose of user-defined reduction declared in namespace
https://bugs.llvm.org/show_bug.cgi?id=38902
Bug ID: 38902
Summary: incorrect diagnose of user-defined reduction declared
in namespace
Product: OpenMP
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Clang Compiler Support
Assignee: unassignedclangb...@nondot.org
Reporter: k...@ca.ibm.com
CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org
template
void bar(T &x, T &y) { x.a += y.a; }
namespace N1
{
struct A { int a; A() : a(0) {} };
#pragma omp declare reduction(+: A : bar(omp_out, omp_in))
};
int main ()
{
N1::A a;
// A a;
#pragma omp parallel reduction(+: a)
{
}
}
$ clang++ -fopenmp d2a.cpp
d2a.cpp:15:34: error: invalid operands to binary expression ('N1::A' and
'N1::A')
#pragma omp parallel reduction(+: a)
^ ~
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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38903] New: assert in clang::TemplateDeclInstantiator::VisitOMPDeclareReductionDecl
https://bugs.llvm.org/show_bug.cgi?id=38903
Bug ID: 38903
Summary: assert in
clang::TemplateDeclInstantiator::VisitOMPDeclareReduct
ionDecl
Product: OpenMP
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Clang Compiler Support
Assignee: unassignedclangb...@nondot.org
Reporter: k...@ca.ibm.com
CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org
struct U
{
void foo(U&, bool);
U();
};
template
struct S
{
int s;
void foo(S &x) {};
#pragma omp declare reduction (foo : U, S : omp_out.foo(omp_in, false))
};
#pragma omp declare reduction (bar : S<1> : omp_out.foo(omp_in))
$ clang++ -fopenmp d3.cpp
clang-8: /llvm/tools/clang/lib/Sema/SemaTemplateInstantiate.cpp:2933:
llvm::PointerUnion*>*
clang::LocalInstantiationScope::findInstantiationOf(const clang::Decl*):
Assertion `isa(D) && "declaration not instantiated in this scope"'
failed.
Stack dump:
...
1. d3.cpp:13:53: current parser token 'foo'
2. d3.cpp:7:8: instantiating class definition 'S<1>'
#0 0x1387ee00 llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/llvm/lib/Support/Unix/Signals.inc:490:0
#1 0x1387ef04 PrintStackTraceSignalHandler(void*)
/llvm/lib/Support/Unix/Signals.inc:553:0
#2 0x1387c568 llvm::sys::RunSignalHandlers()
/llvm/lib/Support/Signals.cpp:66:0
#3 0x1387e4f4 SignalHandler(int)
/llvm/lib/Support/Unix/Signals.inc:343:0
#4 0x3fffad940478 0x478 __GI_abort
#5 0x3fffad940478
#6 0x3fffad940478 __assert_fail_base (+0x478)
#7 0x3fffad3b0d70 __GI___assert_fail (/lib64/libc.so.6+0x40d70)
#8 0x3fffad3a48a4
clang::LocalInstantiationScope::findInstantiationOf(clang::Decl const*)
/llvm/tools/clang/lib/Sema/SemaTemplateInstantiate.cpp:2933:0
#9 0x3fffad3a4994
clang::TemplateDeclInstantiator::VisitOMPDeclareReductionDecl(clang::OMPDeclareReductionDecl*)
/llvm/tools/clang/lib/Sema/SemaTemplateInstantiateDecl.cpp:2750:0
#10 0x17c11620 clang::declvisitor::Base::Visit(clang::Decl*)
/clang/build/tools/clang/include/clang/AST/DeclNodes.inc:503: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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38519] vector IR (insertelement/shufflevector) fails to select for wasm32 with -mattr=+simd128
https://bugs.llvm.org/show_bug.cgi?id=38519 Thomas Lively changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Thomas Lively --- This now lowers to a i8x16.splat instruction, as intended. -- 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 38904] New: thread-safety-analysis doesn't know about std::optional
https://bugs.llvm.org/show_bug.cgi?id=38904
Bug ID: 38904
Summary: thread-safety-analysis doesn't know about
std::optional
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: luka...@chromium.org
CC: llvm-bugs@lists.llvm.org
Repro source code: https://godbolt.org/z/2XG89f (most important parts are
inlined below):
void test2() {
std::optional maybe_autolock;
maybe_autolock.emplace(AutoLock(g_lock));
g_value += 1;
}
For real code where this bug would have mattered see
https://crbug.com/881875#c1 and
services/ws/public/cpp/gpu/context_provider_command_buffer.cc in Chromium which
calls base::Optional::emplace(base::Lock&).
Unexpected error:
:32:3: error: writing variable 'g_value' requires holding mutex
'g_lock' exclusively [-Werror,-Wthread-safety-analysis]
g_value += 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37386] [X86] Scalar masked load/store instrinsics require a 512-bit vector
https://bugs.llvm.org/show_bug.cgi?id=37386 Craig Topper 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34875] [X86] X86movss/X86movsd should select BLENDPS/BLENDPD instruction during isel unless optimizing for size
https://bugs.llvm.org/show_bug.cgi?id=34875 Craig Topper changed: What|Removed |Added Fixed By Commit(s)||r336976 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Craig Topper --- Believe this is fixed after r336976 -- 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 37388] Logic operations on AVX512 __mmask16 do not generate appropriate instructions
https://bugs.llvm.org/show_bug.cgi?id=37388 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||r331847, r331896 --- Comment #4 from Craig Topper --- I'm going to close this. We're doing much better after r331847 and r331896 back in May. Any further issues should be new bugs. -- 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 36300] [x86] Invalid operand expansion for MLOAD
https://bugs.llvm.org/show_bug.cgi?id=36300 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED CC||craig.top...@gmail.com Resolution|--- |FIXED --- Comment #1 from Craig Topper --- I suspect this was largely fixed in r338080. It looks like the main problem was that we split the masked load node into 2 nodes to split the v16i32 types. These nodes are identical and should have been CSEd, but weren't due to the bug fixed in r338080. We legalize one of them and update the operands. Then we legalize the other one and try to update its operands, but now we do detect that they can be CSEed and UpdateNodeOperands doesn't make the update. This leaves us in a situation that PromoteIntegerOperand wasn't prepared for, a non-null SDValue was returned from PromoteIntOp_MLOAD but it wasn't the original node and it has 2 results. With the CSE fixed the 2 identical nodes don't get created from the original split. The test case itself was also made invalid in r338085 when the chain handling for masked loads was improved. Now neither the data result or chain result is used so the node is considered dead and can be deleted. This can be fixed by returning the loaded value. -- 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 38905] New: -Wdocumentation generates error with @see @ref
https://bugs.llvm.org/show_bug.cgi?id=38905
Bug ID: 38905
Summary: -Wdocumentation generates error with @see @ref
Product: clang
Version: 3.9
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: r...@r2air.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
clang++ generates an error on a valid doxygen block that uses the @see tag.
Steps to reproduce:
$ cat docbug.cc
/**
* @see @ref FOO
*/
int function() {
return 0;
}
$ clang++ -Werror -Wdocumentation -c docbug.cc -o docbug.o
Actual result:
docbug.cc:3:8: warning: empty paragraph passed to '@see' command
[-Wdocumentation]
* @see @ref FOO
Expected result:
Doxygen (tested versions 1.8.11 and 1.8.13) interpret this as valid markup.
--
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
