Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2016-01-06 Thread Maciej W. Rozycki
On Fri, 27 Nov 2015, Joseph Myers wrote: > > I find it highly unlikely though that the writers will (be able to) chase > > individual targets and any obscure hardware-dependent options the targets > > may provide. And we cannot expect people compiling software to be > > What that says to me i

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-27 Thread Joseph Myers
On Fri, 27 Nov 2015, Maciej W. Rozycki wrote: > I find it highly unlikely though that the writers will (be able to) chase > individual targets and any obscure hardware-dependent options the targets > may provide. And we cannot expect people compiling software to be What that says to me is tha

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-27 Thread Maciej W. Rozycki
On Fri, 20 Nov 2015, Joseph Myers wrote: > > The target audience for the `-mieee=strict' option is in my idea a > > non-technical user, say a physicist, who does not necessarily know or is > > fluent with the guts of computer hardware and who has the need to build > > and reliably run their so

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-20 Thread Joseph Myers
On Fri, 20 Nov 2015, Maciej W. Rozycki wrote: > The target audience for the `-mieee=strict' option is in my idea a > non-technical user, say a physicist, who does not necessarily know or is > fluent with the guts of computer hardware and who has the need to build > and reliably run their softw

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-20 Thread Maciej W. Rozycki
On Tue, 17 Nov 2015, Joseph Myers wrote: > > Any or all of these options may have effects beyond propagating the IEEE > > Std 754 compliance mode down to the assembler and the linker. In > > particular `-mieee=strict' is expected to guarantee code generated to > > fully comply to IEEE Std 754 ra

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-17 Thread Joseph Myers
On Sat, 14 Nov 2015, Maciej W. Rozycki wrote: > Any or all of these options may have effects beyond propagating the IEEE > Std 754 compliance mode down to the assembler and the linker. In > particular `-mieee=strict' is expected to guarantee code generated to > fully comply to IEEE Std 754 rathe

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-16 Thread Maciej W. Rozycki
On Sat, 14 Nov 2015, Cary Coutant wrote: > > 3.3.2 Static Linking Object Acceptance Rules > > > > The static linker shall follow the user selection as to the linking mode > > used, either of `strict' and `relaxed'. The selection will be made > > according to the usual way assumed for the environ

Re: [RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-14 Thread Cary Coutant
> 3.3.2 Static Linking Object Acceptance Rules > > The static linker shall follow the user selection as to the linking mode > used, either of `strict' and `relaxed'. The selection will be made > according to the usual way assumed for the environment used, which may be > a command-line option, a p

[RFC] MIPS ABI Extension for IEEE Std 754 Non-Compliant Interlinking

2015-11-14 Thread Maciej W. Rozycki
Dear fellow developers, On behalf of Imagination Technologies I would like to introduce the following ABI extension to create a compatibility solution for opposing NaN encodings. I will appreciate your feedback and will happily answer any questions and address any concerns you may have. A c