Bug#114029: gcc-2.95-doc: misleading documentation for -malign-{jump,loop,function}s on sparc

[James Troup <james@nocrew.org>]

Package: gcc-2.95-doc
Version: 2.95.4-0.010902
Severity: minor
[Only a documentation issue and 3.0 drops support for these
 non-portable flags in any event...]

>From the info file:

| `-malign-loops=NUM'
|      Align loops to a 2 raised to a NUM byte boundary.  If
|      `-malign-loops' is not specified, the default is 2.
|
| `-malign-jumps=NUM'
|      Align instructions that are only jumped to to a 2 raised to a NUM
|      byte boundary.  If `-malign-jumps' is not specified, the default
|      is 2.
|
| `-malign-functions=NUM'
|      Align the start of functions to a 2 raised to NUM byte boundary.
|      If `-malign-functions' is not specified, the default is 2 if
|      compiling for 32 bit sparc, and 5 if compiling for 64 bit sparc.

But:

| (base)troup@vore:~$ gcc -o test test.c -malign-loops=2
| cc1: Internal compiler error:
| cc1: -malign-loops=2 is not between 4 and 128 or is not a power of two
| (base)troup@vore:~$ gcc -o test test.c -malign-jumps=2
| cc1: Internal compiler error:
| cc1: -malign-jumps=2 is not between 4 and 128 or is not a power of two
| (base)troup@vore:~$ gcc -o test test.c -malign-functions=2
| cc1: Internal compiler error:
| cc1: -malign-functions=2 is not between 4 and 128 or is not a power of two
| (base)troup@vore:~$

-- 
James