* FIX ME message in osf_sys.c
@ 2014-07-03 17:21 Nick Krause
2014-07-03 18:15 ` Richard Henderson
0 siblings, 1 reply; 3+ messages in thread
From: Nick Krause @ 2014-07-03 17:21 UTC (permalink / raw)
To: rth; +Cc: ink, Matt Turner, linux-alpha, linux-kernel@vger.kernel.org
There seems to be a Fix Me message on line 892 due to info.si_addr = NULL.
I am wondering what value I should declare this variable to instead of Null.
Cheers Nick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FIX ME message in osf_sys.c
2014-07-03 17:21 FIX ME message in osf_sys.c Nick Krause
@ 2014-07-03 18:15 ` Richard Henderson
2014-07-03 18:17 ` Nick Krause
0 siblings, 1 reply; 3+ messages in thread
From: Richard Henderson @ 2014-07-03 18:15 UTC (permalink / raw)
To: Nick Krause; +Cc: ink, Matt Turner, linux-alpha, linux-kernel@vger.kernel.org
On 07/03/2014 10:21 AM, Nick Krause wrote:
> There seems to be a Fix Me message on line 892 due to info.si_addr = NULL.
> I am wondering what value I should declare this variable to instead of Null.
> Cheers Nick
>
The closest thing to compatibility with SIGFPE raised through normal arithmetic
would be the address of the instruction after the callsys that lead to this
system call. Except that's not available without complicating the call to
osf_setsysinfo, and it doesn't seem worth it.
r~
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FIX ME message in osf_sys.c
2014-07-03 18:15 ` Richard Henderson
@ 2014-07-03 18:17 ` Nick Krause
0 siblings, 0 replies; 3+ messages in thread
From: Nick Krause @ 2014-07-03 18:17 UTC (permalink / raw)
To: Richard Henderson
Cc: ink, Matt Turner, linux-alpha, linux-kernel@vger.kernel.org
In that case I will sent a patch removing this FIXME line.
Cheers Nick
On Thu, Jul 3, 2014 at 2:15 PM, Richard Henderson <rth@twiddle.net> wrote:
> On 07/03/2014 10:21 AM, Nick Krause wrote:
>> There seems to be a Fix Me message on line 892 due to info.si_addr = NULL.
>> I am wondering what value I should declare this variable to instead of Null.
>> Cheers Nick
>>
>
> The closest thing to compatibility with SIGFPE raised through normal arithmetic
> would be the address of the instruction after the callsys that lead to this
> system call. Except that's not available without complicating the call to
> osf_setsysinfo, and it doesn't seem worth it.
>
>
> r~
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-07-03 18:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-03 17:21 FIX ME message in osf_sys.c Nick Krause
2014-07-03 18:15 ` Richard Henderson
2014-07-03 18:17 ` Nick Krause
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.