| /external/perfetto/src/traced/probes/ftrace/test/data/android_hammerhead_MRA59G_3.4.0/events/writeback/balance_dirty_pages/ |
| D | format | 23 field:long think; offset:92; size:4; signed:1;
25 …think=%ld", REC->bdi, REC->limit, REC->setpoint, REC->dirty, REC->bdi_setpoint, REC->bdi_dirty, RE…
|
| /external/perfetto/src/traced/probes/ftrace/test/data/android_seed_N2F62_3.10.49/events/writeback/balance_dirty_pages/ |
| D | format | 22 field:long think; offset:88; size:4; signed:1;
24 …think=%ld", REC->bdi, REC->limit, REC->setpoint, REC->dirty, REC->bdi_setpoint, REC->bdi_dirty, RE…
|
| /external/perfetto/src/traced/probes/ftrace/test/data/android_walleye_OPM5.171019.017.A1_4.4.88/events/writeback/balance_dirty_pages/ |
| D | format | 22 field:long think; offset:128; size:8; signed:1;
25 …think=%ld cgroup=%s", REC->bdi, REC->limit, REC->setpoint, REC->dirty, REC->bdi_setpoint, REC->bdi…
|
| /external/perfetto/src/traced/probes/ftrace/test/data/android_flounder_lte_LRX16F_3.10.40/events/writeback/balance_dirty_pages/ |
| D | format | 22 field:long think; offset:128; size:8; signed:1;
24 …think=%ld", REC->bdi, REC->limit, REC->setpoint, REC->dirty, REC->bdi_setpoint, REC->bdi_dirty, RE…
|
| /external/swiftshader/third_party/LLVM/docs/HistoricalNotes/ |
| D | 2000-11-18-EarlyDesignIdeasResp.txt | 7 think so alike!):
61 Yup, I think that this makes a lot of sense. I am still intrigued,
63 think that it could have definite advantages for certain applications
64 (think very small machines, like PDAs). I don't, however, think that our
67 Here are some other auxiliary goals that I think we should consider:
75 x86 and solaris, I think that these two are excellent candidates when
137 time. I think that an epic style of representation (not the instruction
149 Yes yes yes! :) I think it would be *VERY* useful to include this kind
188 I think it makes sense to do so when we get our ideas more formalized and
195 Anyways, let me know what you think about these ideas... and if they sound
|
| D | 2001-02-09-AdveCommentsResponse.txt | 13 > I think your point was that making all types explicit improves clarity
23 %this' and 'bool %that' all over the place, I think it would be
34 > could enable some significant optimizations, though we should think
91 think that we'll have to cast many shifts. :)
137 > A pair of important synchronization instr'ns to think about:
141 What is 'load-linked'? I think that (at least for now) I should add these
151 instruction... and I think that all predicated instructions can possibly
201 > size should not matter. I think we should consider it because I find it
|
| D | 2001-02-09-AdveComments.txt | 13 I think your point was that making all types explicit improves clarity
22 enable some significant optimizations, though we should think about which.
80 o A pair of important synchronization instr'ns to think about:
117 size should not matter. I think we should consider it because I find it
|
| D | 2001-07-06-LoweringIRForCodeGen.txt | 6 BTW, I do think that we should consider lowering the IR as you said. I
8 move-conditional instruction. I don't think we want to put that in the core
|
| D | 2001-05-19-ExceptionResponse.txt | 21 bounded) I don't think this is a big deal. One of the really nice things
38 I think that a code duplication method would be cleaner, and would avoid
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2000-11-18-EarlyDesignIdeasResp.txt | 7 think so alike!):
61 Yup, I think that this makes a lot of sense. I am still intrigued,
63 think that it could have definite advantages for certain applications
64 (think very small machines, like PDAs). I don't, however, think that our
67 Here are some other auxiliary goals that I think we should consider:
75 x86 and solaris, I think that these two are excellent candidates when
137 time. I think that an epic style of representation (not the instruction
149 Yes yes yes! :) I think it would be *VERY* useful to include this kind
188 I think it makes sense to do so when we get our ideas more formalized and
195 Anyways, let me know what you think about these ideas... and if they sound
|
| D | 2001-02-09-AdveCommentsResponse.txt | 13 > I think your point was that making all types explicit improves clarity
23 %this' and 'bool %that' all over the place, I think it would be
34 > could enable some significant optimizations, though we should think
91 think that we'll have to cast many shifts. :)
137 > A pair of important synchronization instr'ns to think about:
141 What is 'load-linked'? I think that (at least for now) I should add these
151 instruction... and I think that all predicated instructions can possibly
201 > size should not matter. I think we should consider it because I find it
|
| D | 2001-02-09-AdveComments.txt | 13 I think your point was that making all types explicit improves clarity
22 enable some significant optimizations, though we should think about which.
80 o A pair of important synchronization instr'ns to think about:
117 size should not matter. I think we should consider it because I find it
|
| D | 2001-07-06-LoweringIRForCodeGen.txt | 6 BTW, I do think that we should consider lowering the IR as you said. I
8 move-conditional instruction. I don't think we want to put that in the core
|
| D | 2001-05-19-ExceptionResponse.txt | 21 bounded) I don't think this is a big deal. One of the really nice things
38 I think that a code duplication method would be cleaner, and would avoid
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/HistoricalNotes/ |
| D | 2000-11-18-EarlyDesignIdeasResp.txt | 7 think so alike!):
61 Yup, I think that this makes a lot of sense. I am still intrigued,
63 think that it could have definite advantages for certain applications
64 (think very small machines, like PDAs). I don't, however, think that our
67 Here are some other auxiliary goals that I think we should consider:
75 x86 and solaris, I think that these two are excellent candidates when
137 time. I think that an epic style of representation (not the instruction
149 Yes yes yes! :) I think it would be *VERY* useful to include this kind
188 I think it makes sense to do so when we get our ideas more formalized and
195 Anyways, let me know what you think about these ideas... and if they sound
|
| D | 2001-02-09-AdveCommentsResponse.txt | 13 > I think your point was that making all types explicit improves clarity
23 %this' and 'bool %that' all over the place, I think it would be
34 > could enable some significant optimizations, though we should think
91 think that we'll have to cast many shifts. :)
137 > A pair of important synchronization instr'ns to think about:
141 What is 'load-linked'? I think that (at least for now) I should add these
151 instruction... and I think that all predicated instructions can possibly
201 > size should not matter. I think we should consider it because I find it
|
| D | 2001-02-09-AdveComments.txt | 13 I think your point was that making all types explicit improves clarity
22 enable some significant optimizations, though we should think about which.
80 o A pair of important synchronization instr'ns to think about:
117 size should not matter. I think we should consider it because I find it
|
| D | 2001-07-06-LoweringIRForCodeGen.txt | 6 BTW, I do think that we should consider lowering the IR as you said. I
8 move-conditional instruction. I don't think we want to put that in the core
|
| D | 2001-05-19-ExceptionResponse.txt | 21 bounded) I don't think this is a big deal. One of the really nice things
38 I think that a code duplication method would be cleaner, and would avoid
|
| /external/curl/tests/data/ |
| D | test805 | 37 Hello Joe, do you think we can meet at 3:30 tomorrow?
59 Hello Joe, do you think we can meet at 3:30 tomorrow?
|
| /external/ltp/testcases/open_posix_testsuite/functional/semaphores/ |
| D | sem_philosopher.c | 35 int think(int ID) in think() function
76 think(PhID); in philosopher()
|
| /external/ltp/testcases/open_posix_testsuite/functional/timers/ |
| D | plan.txt | 16 absolute timer, no repeat think: alarm clock
17 relative timer, no repeat think: stopwatch
18 absolute timer, repeats think: grandfather clock
19 relative timer, repeats think: repeating stopwatch
|
| /external/libpcap/ |
| D | TODO | 10 autogen.sh script to run autoconf etc. after checkout. I think we
24 + not very well suited for interactive programs (think ethereal). There
|
| /external/v8/tools/memory/asan/ |
| D | blacklist_win.txt | 4 # Please think twice before you add or remove these rules.
|
| D | blacklist.txt | 4 # Please think twice before you add or remove these rules.
|