Home
last modified time | relevance | path

Searched refs:thinking (Results 1 – 25 of 86) sorted by relevance

1234

/external/ltp/testcases/open_posix_testsuite/functional/semaphores/
Dsem_philosopher.c26 #define thinking 0 macro
98 state[PhID] = thinking; in philosopher()
/external/cldr/tools/java/org/unicode/cldr/icu/
Dmakefile_header.txt7 # If you are thinking of modifying this file, READ THIS.
/external/autotest/client/bin/
DTODO9 (MJB: I was thinking of kernel compiles I guess. Maybe we should just
/external/cldr/tools/c/genldml/resources/
Dgenldml_resources.mak34 # -t fools make into thinking there are files such as es.res, etc
/external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/Hexagon/
Dpacketize-l2fetch.ll5 ; was tricked into thinking that it's a store. The v65-specific
/external/icu/icu4c/source/samples/ufortune/resources/
Dfortune_resources.mak45 # -t fools make into thinking there are files such as es.res, etc
/external/iproute2/tc/
DREADME.last8 manually and after a bit of thinking in <include/net/pkt_sched.h>
/external/llvm/docs/HistoricalNotes/
D2001-02-13-Reference-Memory.txt27 After thinking about it, this model has two problems:
D2001-02-13-Reference-MemoryResponse.txt27 > After thinking about it, this model has two problems:
D2000-11-18-EarlyDesignIdeas.txt28 a. A single-assignment VM, which we've both already been thinking about.
D2001-02-06-TypeNotationDebateResp1.txt34 thinking about it. Honestly, I don't find it much easier than the C syntax.
D2000-11-18-EarlyDesignIdeasResp.txt58 > a. A single-assignment VM, which we've both already been thinking
106 C. In the model I was thinking of (subject to change of course), we
/external/swiftshader/third_party/llvm-7.0/llvm/docs/HistoricalNotes/
D2001-02-13-Reference-Memory.txt27 After thinking about it, this model has two problems:
D2001-02-13-Reference-MemoryResponse.txt27 > After thinking about it, this model has two problems:
D2000-11-18-EarlyDesignIdeas.txt28 a. A single-assignment VM, which we've both already been thinking about.
D2001-02-06-TypeNotationDebateResp1.txt34 thinking about it. Honestly, I don't find it much easier than the C syntax.
D2000-11-18-EarlyDesignIdeasResp.txt58 > a. A single-assignment VM, which we've both already been thinking
106 C. In the model I was thinking of (subject to change of course), we
D2001-02-06-TypeNotationDebateResp4.txt27 > thinking about it. Honestly, I don't find it much easier than the C syntax.
/external/swiftshader/third_party/LLVM/docs/HistoricalNotes/
D2001-02-13-Reference-Memory.txt27 After thinking about it, this model has two problems:
D2001-02-13-Reference-MemoryResponse.txt27 > After thinking about it, this model has two problems:
D2000-11-18-EarlyDesignIdeas.txt28 a. A single-assignment VM, which we've both already been thinking about.
D2001-02-06-TypeNotationDebateResp1.txt34 thinking about it. Honestly, I don't find it much easier than the C syntax.
D2000-11-18-EarlyDesignIdeasResp.txt58 > a. A single-assignment VM, which we've both already been thinking
106 C. In the model I was thinking of (subject to change of course), we
/external/python/cpython2/Misc/
DPorting39 module; this is the time to start thinking about what to do with the
/external/python/cpython2/Misc/Vim/
Dvimrc77 " UCS encoding (WARNING: can trick shells into thinking a text file is actually

1234