Alan Stern wrote:
Do we support gcc --combine already ?
As far as I know, the only advantage of gcc -combine is that it allows
the optimizer to work on more than one file at a time. Would that
really make any significant difference for these particular source
files?
It should also remove static functions which are not used. However I
really don't know the root cause of the memory footprint.
Having every file as a separate module might be a little overkill because
you need usually ~2 guard pages per module in virtual address space. Maybe
a "library" like module.
Alan Stern
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
