> > +@table @gcctabopt > > + > > +@item -mspace > > +@opindex mspace > > +Enable code-size optimizations. > > +Some of these optimizations incur a minor performance penalty. > > We already have -Os, so why is an architecture-specific option for this > needed?
Code compiled with -mspace is somewhat slower than code without. So we typically build *all* code with -Os, with everything non-critical also compiled -mspace. Is this a legitimate option or should I just use -Os? -- James Bowman FTDI Open Source Liaison
