Home
last modified time | relevance | path

Searched refs:Consider (Results 1 – 25 of 197) sorted by relevance

12345678

/openbsd-src/gnu/llvm/compiler-rt/lib/lsan/
H A Dlsan_flags.inc41 LSAN_FLAG(bool, use_unaligned, false, "Consider unaligned pointers valid.")
43 "Consider pointers found in poisoned memory to be valid.")
/openbsd-src/gnu/usr.bin/perl/pod/
H A Dperlstyle.pod271 might want to do something like it again? Consider generalizing your
272 code. Consider writing a module or object class. Consider making your
274 effect. Consider giving away your code. Consider changing your whole
275 world view. Consider... oh, never mind.
/openbsd-src/gnu/gcc/gcc/config/m68k/
H A Dm68k.opt125 Consider type 'int' to be 32 bits wide
145 Consider type 'int' to be 16 bits wide
/openbsd-src/gnu/gcc/gcc/config/h8300/
H A Dh8300.opt47 Consider access to byte sized memory slow
/openbsd-src/gnu/llvm/llvm/docs/
H A DInstrRefDebugInfo.md22 and operand position that the value is defined in. Consider the LLVM IR way of
33 codegen backend of LLVM, after instruction selection. Consider the X86 assembly
155 operand pair to new instruction number / operand pair. Consider if we replace
H A DDebuggingJITedCode.rst61 Consider the following C code (with line numbers added to make the example
H A DInAlloca.rst110 Consider the evaluation of:
H A DGetElementPtr.rst65 therefore be indexed and requires an index operand. Consider this example:
216 index. Consider this example:
236 through the 0th element does not change the address. Consider this example:
H A DMergeFunctions.rst326 Consider how type comparison works.
382 Consider the situation when we're looking at the same place in left
400 Consider a small example here:
482 1. We have to start with the bad news. Consider function self and
/openbsd-src/gnu/llvm/llvm/lib/Target/WebAssembly/
H A DREADME.txt81 Consider implementing optimizeSelect, optimizeCompareInstr, optimizeCondBranch,
141 coloring. Consider experimenting with the MachineScheduler (enable via
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/lldb/source/API/
H A DBUILD.gn3 # FIXME: Consider making it a shared_library everywhere like in cmake?
/openbsd-src/gnu/usr.bin/perl/hints/
H A Daix_3.sh146 *** Consider upgrading your C compiler, or getting the GNU cc (gcc).
H A Daix_4.sh200 *** Consider upgrading your C compiler, or getting the GNU cc (gcc).
H A Dhpux.sh650 Consider upgrading to at least HP-UX 11.
/openbsd-src/gnu/lib/libiberty/src/
H A DREADME44 * Consider the special cases of building libiberty; as of this
/openbsd-src/gnu/llvm/libcxx/docs/DesignDocs/
H A DUnspecifiedBehaviorRandomization.rst8 Consider the follow snippet which steadily happens in tests:
H A DUniquePtrTrivialAbi.rst8 Consider the follow snippets
/openbsd-src/gnu/llvm/clang/docs/
H A DTooling.rst14 you want to use. Consider the other interfaces only when you have a good
/openbsd-src/gnu/llvm/llvm/lib/Target/X86/
H A DREADME-SSE.txt207 Consider:
230 Here's a sick and twisted idea. Consider code like this:
521 Consider:
716 Consider using movlps instead of movsd to implement (scalar_to_vector (loadf64))
H A DREADME-X86-64.txt155 Consider the following (contrived testcase, but contains common factors):
/openbsd-src/gnu/llvm/llvm/lib/Target/ARM/
H A DREADME.txt20 Crazy idea: Consider code that uses lots of 8-bit or 16-bit values. By the
143 * Consider this silly example:
301 2) Consider spliting a indexed load / store into a pair of add/sub + load/store
635 Consider the following simple C code:
/openbsd-src/gnu/llvm/llvm/lib/CodeGen/
H A DREADME.txt119 crop up unpredictably. Consider:
/openbsd-src/gnu/llvm/lld/docs/ELF/
H A Dwarn_backrefs.rst77 libraries like ``B``. Consider linking ``B`` with object semantics by
/openbsd-src/gnu/gcc/gcc/config/mt/
H A DABI.txt116 Consider the parameters in a function call as ordered from left (first
/openbsd-src/gnu/gcc/gcc/config/iq2000/
H A Dabi124 Consider the parameters in a function call as ordered from left (first

12345678