Searched refs:expanding (Results 1 – 17 of 17) sorted by relevance
521 if (fn->expanding) in inline_function()524 fn->expanding = 1; in inline_function()565 fn->expanding = 0; in inline_function()
173 expanding:1, member
759 struct ident *expanding = token->ident; in expand() local764 if (expanding->tainted) { in expand()777 expanding->tainted = 1; in expand()
517 u_int32_t num_items, const u_int8_t expanding) in __addel() argument519 __addel(hashp, item_info, key, val, num_items, expanding) in __addel()524 const u_int32_t expanding;592 if (!expanding)599 if (expanding)
103 # There were some issues with expanding a SrcList object using a call
135 I am interested in expanding this list so please let me know if you
104 the wrong state after expanding with ${arr[@]} has been fixed. 176 12-03-23 A bug in lowercase and uppercase fields when expanding ${name:=val}223 from expanding later in a program has been fixed.681 are expanded each time they are referenced rather than expanding688 10-08-04 A bug in the expanding of variables whose names contain multibyte1312 08-07-30 A bug in which expanding compound variable that had a get discipline1505 07-09-18 The value of ${!var[sub]} was not expanding to var[sub] and this2086 03-07-15 An error in which expanding an indexed array inside a compound2134 .sh. prefixed to it after expanding a variable whose name begins
1317 can be followed by a number representing the numeric base when expanding1924 When patterns are used to generate pathnames when expanding
1206 boolean_t expanding = (oldc != 0); in vdev_metaslab_init() local1222 if (expanding) { in vdev_metaslab_init()1276 if (!expanding && !vd->vdev_removing) { in vdev_metaslab_init()
235 / macros for expanding S-box data
833 @ MSG_MOVE_PAREXPN "expanding symbol=%s into .data: %s"1615 # Section messages (used when expanding segment information)
155 from keeping up with the demands of its quickly-expanding user base. In
2711 % \endtemplate) expanding \doitemize.6594 % Append the tokens #2 to the definition of macro #1, not expanding either.
204 from keeping up with the demands of its quickly-expanding user base. In
156 from keeping up with the demands of its quickly-expanding user base. In
536 # shall I avoid expanding CNAMEs (violates protocols)?
948 # midnight. To save (energy?) consumption, we're expanding Summer Time