Lines Matching full:look
4379 check does not look for the string `"error"' unless it is part of
4388 check does not look for the string `"warning"' unless it is part
5313 brief description of how a new pass should use it. I need to look at
6345 as you might expect, given its name!) You can look at the
7179 tree structure; back ends must look at the `DECL_CONTEXT' for the
11020 This will not work, several of the optimizers only look at
11667 look different from OP, but they will be equal at run time. If the
14614 So if you want to look at the use pointers for all the `USE' and
14640 you want to look at are the `VDEF's together, there is a fourth
14663 /* Look at every virtual PHI use. */
14669 /* Look at every real PHI use. */
14673 /* Look at every PHI use. */
16654 RTL expressions which show what the instruction should look like.
16943 An insn that matches this pattern might look like:
17662 would say, "That does not look like an add instruction; try other
17666 the constraint true. The results might look like this:
19534 no side effects, and it cannot look at the operand. The usual use
20158 `find_reg_note' and look for a `REG_UNUSED' note on the quotient
20389 RTL pattern should look like this:
20396 RTL pattern should look like this:
21338 look like
22104 The `include' pattern tells the compiler tools where to look for
22309 INSN-PATTERN-1 and so on look _almost_ like the second operand of
23290 look more accurately at reservations of states.
28129 C compiler and look at the assembler code that results.
28487 its cache line. Look in `m68k.h' as a guide.
28563 to deposit the value of `EDOM' into `errno' directly. Look in
28700 When you see a `const', you will have to look inside it to find the
29111 to ordered one. Then definition may look like:
31308 If you need to look at the operand values, they can be found as the
33254 variable that specifies where the linker should look for libraries.
34155 what parts of the source to look at. All `struct' and `union'
37234 look up both forms.
