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

2017-10-18 Thread Matthew Fortune
Hi Maciej, Slow thread, sorry for dragging it out further... Maciej Rozycki writes: > On Fri, 11 Nov 2016, Matthew Fortune wrote: > > > This means that a user consciously creating an object that 'needs' > ieee > > compliance via use of -fieee=strict or -mieee=strict is thwarted by > the > > nex

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

2017-08-24 Thread Maciej W. Rozycki
Hi Matthew, On Fri, 11 Nov 2016, Matthew Fortune wrote: > This means that a user consciously creating an object that 'needs' ieee > compliance via use of -fieee=strict or -mieee=strict is thwarted by the > next user who builds the executable. This kind of scenario can occur with > a static librar

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

2016-11-11 Thread Matthew Fortune
Maciej Rozycki writes: > I'm back to this effort now, thanks for patience. Likewise, this thread got buried in email. At the risk of further delaying this work I do still have issues with the design. > > > 3.4 Relocatable Object Generation > > > > > > Tools that produce relocatable objects suc

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

2016-07-25 Thread Joseph Myers
On Thu, 14 Jul 2016, Maciej W. Rozycki wrote: > 2. An idea has been proposed to have objects marked by the assembler to >indicate whether they include an FP hardware instruction or not. The >latters would automatically become don't-cares as far as NaN encoding >is concerned and if a

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

2016-07-13 Thread Maciej W. Rozycki
Hi Matthew, I'm back to this effort now, thanks for patience. > Thanks for the update. I've read through the whole proposal again and > it looks good. I'd like to discuss legacy objects a bit more though... Thanks for your review. > > 3.4 Relocatable Object Generation > > > > Tools that p

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

2016-05-16 Thread Matthew Fortune
Hi Maciej, Thanks for the update. I've read through the whole proposal again and it looks good. I'd like to discuss legacy objects a bit more though... Maciej Rozycki writes: > 3.4 Relocatable Object Generation > > Tools that produce relocatable objects such as the assembler shall > always p

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

2016-05-14 Thread Maciej W. Rozycki
Dear fellow developers, Here is the second revision of the ABI extension specification previously posted, incorporating feedback received for the first revision. Changes have been made to Section 4 "Implementation Notes", the remaining parts have stayed the same. The master copy of this docum