Fixincludes has two ways of doing things: "oneprocess" and "twoprocess".
It appears that oneprocess is more often used, presumably slightly faster, but
that twoprocess is more portable and would work everywhere oneprocess is used.
Suggest just keeping one portable form and removing the other.
Less code to maintain and less autoconfing is generally better, unless the
advantages are sufficient to motivate the extra work and reduced portability.
--
Summary: suggest drop fixincludes oneprocess and just maintain
twoprocess
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jay dot krell at cornell dot edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44331
