Lines Matching full:safe
7350 break from the loop without using this macro. It is safe to simply
8752 is safe to assume that all comparison operations have format `ee'.
10640 register is implicitly used in an insn. It is also safe to use in
11527 RTL structure; in other words, it is safe to do a tree-walk of all
11707 of the `basic_block' data type point to type-safe vectors of edges to
12165 safe, as functions to implement them already know how to update
13326 registers is safe provided its predicate rejects registers.
13328 An operand whose predicate accepts only constant values is safe
13336 register, it is certain to be safe. It need not permit all
17353 It is safe to omit constraints in all the operands of the peephole; or
21039 definition is safe:
21282 It is always safe to define this macro with a nonzero value, but
22926 pointer; in other words, if it is safe to delete an instruction to
22931 which frame pointers are maintained. It is never safe to delete a
23612 It is always safe for this macro to not be defined. It exists so
23637 In fact, it is safe to omit this macro. But often a
23926 A C expression whose value is one if it is always safe to reverse a
24771 In the case of a constant, it is safe to assume that the rtl is a
25676 These names are safe on most systems, but make debugging difficult
27140 bytes. It's safe to assume that the data was created by the same
27365 assume that it is safe to omit a sign-extend, zero-extend, and
27405 otherwise. This definition is always safe, but if
27411 A C expression which is nonzero if on this machine it is safe to
27732 Define this macro as a C expression that is nonzero if it is safe
27743 Define this macro as a C expression that is nonzero if it is safe
28053 This target hook returns `true' if it is safe to use a local alias
28759 This is somewhat dangerous; the only safe use is in a union when
30328 forth). Later, more work on MT-safe string and shadow headers.
30527 * Teemu Torma for thread safe exception handling support.
