Searched refs:worst (Results 1 – 13 of 13) sorted by relevance
40 * Assume GD32L23X use the worst implementation, set the max erase
31 environment differences. Last and worst: new signing feature and options are
17 with features available through the compiler, we can also generate worst-case190 To view worst-case stack usage analysis, build this with the
66 size makes each measure roughly 42µs slower in the worst case.
82 worst-case latency.
66 * Assume GD32E50x use the worst implementation, set the max erase
247 that, in worst scenario, value provided here may cause FATFS
93 the second core to the worst-case scenario from TF-M.
997 int "Number of connections with worst-case overlapping procedures"1001 Set the number connections for which worst-case buffer requirements
246 controller. Number of required RX buffers would worst-case be
140 denial of service in the best case, or code execution in the worst1814 A rogue thread can corrupt the gp reg and cause the entire system to hard fault at best, at worst,
58 # the worst-case stack size if an out-of-tree controller is used.
1234 * :github:`30679` - puncover worst-case stack analysis does not work
