Searched refs:push (Results 1 – 5 of 5) sorted by relevance
| /busybox-1.35.0/miscutils/ |
| D | dc.c | 46 static void push(double a) in push() function
62 push(pop() + pop()); in add()
69 push(pop() - subtrahend); in sub()
74 push(pop() * pop()); in mul()
82 push(pow(pop(), topower)); in power()
90 push(pop() / divisor); in divide()
105 push(0); in mod()
110 push((data_t) pop() % d); in mod()
115 push((data_t) pop() & (data_t) pop()); in and()
120 push((data_t) pop() | (data_t) pop()); in or()
[all …]
|
| D | bc.c | 5863 static BC_STATUS zdc_program_assignStr(BcResult *r, BcVec *v, bool push) in zdc_program_assignStr() argument
5872 if (!push) { in zdc_program_assignStr()
|
| /busybox-1.35.0/docs/ |
| D | contributing.txt | 262 to the mailing list, and especially before you push a change to Git. Here
387 coder, you may be invited to become a committer, thus enabling you to push
389 someone else to push your change for you, you can just do it yourself.
392 should test your changes before you push them. You should also talk to an
397 For more information on Git push access, see:
405 Generally, you should feel free to push a change if:
412 The more of the above are true, the better it is to just push a change
419 Even if you have push access, you should probably still post a patch to the
|
| /busybox-1.35.0/scripts/kconfig/ |
| D | lex.zconf.c_shipped | 1600 YY_FATAL_ERROR( "flex scanner push-back overflow" );
1871 /* Only push if top exists. Otherwise, replace top. */
1902 * Guarantees space for at least one push.
1928 /* Increase the buffer to prepare for a possible push. */
|
| /busybox-1.35.0/shell/ |
| D | ash.c | 9848 pushlocalvars(int push) in pushlocalvars() argument
9854 if (!push) in pushlocalvars()
11132 setinputfd(int fd, int push) in setinputfd() argument
11134 if (push) { in setinputfd()
|