From: groepaz (groepaz_at_gmx.net)
Date: 2002-05-23 21:30:41
Hello Ullrich, >> thats why i suggested using "real" (IEEE) floats in the compiler >> internally, and use IEEE for internal conversion and arithmetics, but >> apart from that let the assembler know about different targets formats >> (and also IEEE for that matter) - and then simply spill calls to a >> standard fp-emulator interface.... UvB> This is ok with me. But to get the interface right, I would like to have the UvB> first implementation to be a IEEE one. If you want to use the ROM routines UvB> later, and it is possible to plug them into the existing interface - ok. But UvB> I'm convinced that using non standard routines for a start will spoil the UvB> interface and prevent standard compliant routines later. ok....THAT reason i can perfectly accept ;=P >> so the real question is, how can the user (me) use his non-standard >> libraries with your compiler without the need of adding "ugly" stuff >> to the compiler that potentially breaks the standard ? UvB> My proposal would be to add standard compliant floating point routines (if UvB> any). These routines need an interface, and you can then go ahead and replace UvB> these routines with your own. ok then......mmmmhhh..... any pointers to the required standard and maybe a reference implementation in C ? :o) -- Best regards, groepaz mailto:groepaz_at_gmx.net ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-05-23 21:29:05 CEST