Searched full:tightly (Results 1 – 25 of 71) sorted by relevance
123
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | cond-op-not.mk | 16 # The ! binds more tightly than the &&.
21 # The operator '==' binds more tightly than '!'.
|
| H A D | cond-op.mk | 11 # In make, && binds more tightly than ||, like in C.
14 # If || were to bind more tightly than &&, the result would be different
|
| /freebsd/usr.sbin/nfsd/ |
| H A D | pnfs.4 | 101 .Dq tightly coupled
158 .Dq tightly coupled
|
| /freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | arm,nvic.txt | 3 The NVIC provides an interrupt controller that is tightly coupled to
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | ingenic,pinctrl.txt | 7 For the XBurst SoCs, pin control is tightly bound with GPIO ports. All pins may
|
| H A D | ingenic,pinctrl.yaml | 14 For the Ingenic SoCs, pin control is tightly bound with GPIO ports. All pins
|
| /freebsd/share/man/man4/ |
| H A D | ath_hal.4 | 77 and the code is tightly integrated with the driver.
|
| H A D | dtrace_fbt.4 | 269 probes are by definition tightly coupled to kernel code; if the code underlying
|
| /freebsd/contrib/mandoc/ |
| H A D | tbl.3 | 63 This library is tightly integrated into the
|
| H A D | eqn.7 | 404 In the following list, earlier operations bind more tightly than
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/ |
| H A D | CommandFlags.h | 166 /// Common utility function tightly tied to the options listed here. Initializes
|
| /freebsd/sys/contrib/device-tree/src/arm64/ti/ |
| H A D | k3-am62-mcu.dtsi | 150 /* Tightly coupled to M4F */
|
| H A D | k3-am62a-mcu.dtsi | 151 /* Tightly coupled to M4F */
|
| H A D | k3-am62p-mcu.dtsi | 149 /* Tightly coupled to M4F */
|
| H A D | k3-am62p-j722s-common-mcu.dtsi | 160 /* Tightly coupled to M4F */
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/Scalar/ |
| H A D | LoopInterchange.cpp | 223 // The current loop has multiple subloops in it hence it is not tightly in populateWorklist()
552 LLVM_DEBUG(dbgs() << "Checking if loops are tightly nested\n"); in tightlyNested()
813 // We already made sure that the loop nest is tightly nested. in currentLimitations()
1002 // Check if the loops are tightly nested. in canInterchangeLoops()
1004 LLVM_DEBUG(dbgs() << "Loops not tightly nested\n"); in canInterchangeLoops()
1009 << "Cannot interchange loops because they are not tightly " in canInterchangeLoops()
|
| /freebsd/share/man/man9/ |
| H A D | hhook.9 | 67 frameworks are tightly integrated.
|
| H A D | khelp.9 | 73 frameworks are tightly integrated and anyone interested in
|
| /freebsd/sys/nfsclient/ |
| H A D | nfsnode.h | 95 * be well aligned and, therefore, tightly packed.
|
| /freebsd/sys/fs/nfsclient/ |
| H A D | nfsnode.h | 91 * be well aligned and, therefore, tightly packed.
|
| /freebsd/contrib/kyua/utils/signals/ |
| H A D | interrupts_test.cpp | 92 /// the class but is tightly related.
|
| /freebsd/lib/libthr/ |
| H A D | libthr.3 | 50 The library is tightly integrated with the run-time link editor
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | common.yaml | 21 have to be tightly coupled with the LED device binding. They are represented
|
| /freebsd/sys/dev/bhnd/bhndb/ |
| H A D | bhndb_pcireg.h | 82 * [0x0000+0x????] fixed ARM tightly-coupled memory (TCM).
|
| /freebsd/sys/contrib/device-tree/Bindings/remoteproc/ |
| H A D | xlnx,zynqmp-r5fss.yaml | 69 tightly coupled memories (TCM). System memory is cacheable, but the TCM
|
123