Re: -pie is broken on hppa

> On the console, there's a continuous stream of messages:
> 
>      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
>      PSW: 00001000000001101111111100001111 Not tainted
> r00-03  000000ff0806ff0f 000000004036c000 0000000040104edc 00000000c0601048
> r04-07  00000000403d79d4 00000000403d89d4 000000000002c258 0000000000000000
> r08-11  000000000002a3f4 000000000002a3f4 0000000000000001 0000000000000000
> r12-15  000000000002a3f4 0000000000000000 0000000000000001 000000000002c258
> r16-19  000000000002a3f4 000000000002a3f4 000000000002a3f4 0000000000000000
> r20-23  000000000000012a 000000004029c000 0000000040357594 000000000002c268
> r24-27  00000000c0601048 0000000000000058 000000000002c258 0000000040503fc0
> r28-31  00000000403daf60 000000007c744170 000000007c744180 00000000403575e3
> sr00-03  00000000000eb800 0000000000000000 0000000000000000 00000000000eb800
> sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
> 
> IASQ: 0000000000000000 0000000000000000 IAOQ: 0000000000000000 0000000000000004
>  IIR: 00000000    ISR: 00000000000eb800  IOR: 0000000000000000
>  CPU:        0   CR30: 000000007c744000 CR31: 00000000404c4000
>  ORIG_R28: 0000000040155a7c
>  IAOQ[0]: 0x0
>  IAOQ[1]: 0x4
>  RP(r2): syscall_exit+0x0/0x14

The kernel is 2.6.20-gfb60ab85-dirty.  The above appears to be a
syscall that's not hooked up.   The number appears to be 0x12a (298).

I believe that we aren't allowed to fault on the gateway page.
If we have holes in the syscall table, I think we need a check
for this since the following code will fault if r19 is zero:

.Lin_syscall:
        ldil    L%syscall_exit,%r2
	be      0(%sr7,%r19)
	ldo     R%syscall_exit(%r2),%r2

Dave
-- 
J. David Anglin                                  [email protected]
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)