diff options
| author | John David Anglin <dave.anglin@bell.net> | 2014-09-23 02:54:50 +0200 |
|---|---|---|
| committer | Helge Deller <deller@gmx.de> | 2014-09-23 21:38:26 +0200 |
| commit | d26a7730b5874a5fa6779c62f4ad7c5065a94723 (patch) | |
| tree | a2adfcdfd9184222fe57453c5a3400bb847df511 /arch | |
| parent | parisc: pdc_stable.c: Avoid potential stack overflows (diff) | |
| download | linux-d26a7730b5874a5fa6779c62f4ad7c5065a94723.tar.xz linux-d26a7730b5874a5fa6779c62f4ad7c5065a94723.zip | |
parisc: Only use -mfast-indirect-calls option for 32-bit kernel builds
In spite of what the GCC manual says, the -mfast-indirect-calls has
never been supported in the 64-bit parisc compiler. Indirect calls have
always been done using function descriptors irrespective of the
-mfast-indirect-calls option.
Recently, it was noticed that a function descriptor was always requested
when the -mfast-indirect-calls option was specified. This caused
problems when the option was used in application code and doesn't make
any sense because the whole point of the option is to avoid using a
function descriptor for indirect calls.
Fixing this broke 64-bit kernel builds.
I will fix GCC but for now we need the attached change. This results in
the same kernel code as before.
Signed-off-by: John David Anglin <dave.anglin@bell.net>
Cc: stable@vger.kernel.org # v3.0+
Signed-off-by: Helge Deller <deller@gmx.de>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/parisc/Makefile | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/arch/parisc/Makefile b/arch/parisc/Makefile index 7187664034c3..5db8882f732c 100644 --- a/arch/parisc/Makefile +++ b/arch/parisc/Makefile @@ -48,7 +48,12 @@ cflags-y := -pipe # These flags should be implied by an hppa-linux configuration, but they # are not in gcc 3.2. -cflags-y += -mno-space-regs -mfast-indirect-calls +cflags-y += -mno-space-regs + +# -mfast-indirect-calls is only relevant for 32-bit kernels. +ifndef CONFIG_64BIT +cflags-y += -mfast-indirect-calls +endif # Currently we save and restore fpregs on all kernel entry/interruption paths. # If that gets optimized, we might need to disable the use of fpregs in the |