Searched refs:Moving (Results 1 – 18 of 18) sorted by relevance
3 Moving globalized variable to the stack. [OMP110]48 omp110.cpp:6:7: remark: Moving globalized variable to the stack. [OMP110]73 /usr/include/c++/8/complex:328:20: remark: Moving globalized variable to the stack. [OMP110]76 /usr/include/c++/8/complex:388:20: remark: Moving globalized variable to the stack. [OMP110]
74 missed.cpp:4:7: remark: Moving globalized variable to the stack. [OMP110]
65 - Moving globalized variable to the stack.
7 ; Moving the DIV32r instruction exercises the regunit update code because44 ; Moving a use below the existing kill (%5):45 ; Moving a tied virtual register def (%11):
250 ; - Moving instruction around (mainly sext when promoting instruction).
57 ; CHECK: remark: /tmp/kk.c:2:22: Moving accesses to memory location out of the loop
11 ; CHECK-REMARKS: remark: remove_globalization.c:2:2: Moving globalized variable to the stack.12 ; CHECK-REMARKS: remark: remove_globalization.c:6:2: Moving globalized variable to the stack.
214 ; Moving SP, access via SP475 ; Moving SP, access via SP.
36 used through multiple stack frames. Moving such objects away from the safe
877 :arc-term:`Moving` occurs in specific situations where an lvalue is "moved
2 Moving LLVM Projects to GitHub225 * Moving code across sub-project (during refactoring for instance) in a single544 Moving Local Branches to the Monorepo
69 * Moving instructions between basic blocks. For example, if instruction ``I1``
737 #. Moving loop invariant loads and calls out of loops. If we can determine
521 // Test Case: Moving invalid DeallocOp (there is a user after deallocation) in a
4719 bool Moving = ImplicitInitKind == IIK_Move; in BuildImplicitBaseInitializer() local4736 if (Moving) { in BuildImplicitBaseInitializer()4744 Moving ? VK_XValue : VK_LValue, in BuildImplicitBaseInitializer()4789 bool Moving = ImplicitInitKind == IIK_Move; in BuildImplicitMemberInitializer() local4804 if (Moving) { in BuildImplicitMemberInitializer()
690 Moving arg1 onto the stack slot of callee function would overwrite
4352 // Moving from XMM to XMM and clear upper 64 bits. Note, there is a bug in
1598 // Moving 32-bit values between GPRs and FPRs can be done using VLVGF