On Fri, 2016-07-08 at 07:11 -0500, Segher Boessenkool wrote: > On Fri, Jul 08, 2016 at 12:42:34PM +0200, Bernd Schmidt wrote: > > On 06/14/2016 11:24 PM, Segher Boessenkool wrote: > > > On Wed, Jun 08, 2016 at 06:43:23PM +0200, Bernd Schmidt wrote: > > > > On 06/08/2016 05:16 PM, Segher Boessenkool wrote: > > > > > There is no standard naming for this as far as I know. I'll > > > > > gladly > > > > > use a better name anyone comes up with. > > > > > > > > Maybe just subpart? > > > > > > How about "factor"? > > > > Still sounds odd to me. "Component" maybe? Ideally a native speaker > > would help decide what sounds natural to them. > > That does sound nice... OTOH, > > $ grep -i component *.c|wc -l > 1081 > > but the opportunity for confusion is limited I think (and calling it > "shrink-wrapping component" where needed sounds natural too!)
As far as I understand the idea, there are a number of target-specific things that are to be done during a function call, and the optimization tries to detect which of optimize each of these separately. Some synonyms and near-synonyms for these "things": aspect component concern duty element facet factor item part piece portion responsibility and I suppose "shrink_wrap_part" is shorter than "shrink_wrap_component". (Yeah, I'm bike-shedding; sorry)
