Steve Capper dixit:>> Do we need the fpregs saved even though klibc doesn't do fp?>For gcc targetting Aarch64, We can only guarantee that d8-d15 are >left alone when -mgeneral-regs-only is supplied for building klibc >and any software linked against klibc. I would much prefer toWe can enforce this in klcc, just like -mregparm=3 is used by the i386 target. bye, //mirabilos -- ?Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.? -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: ?[?]uhr.gz is a reason to install mksh on every system.?)
Yes, that is not an issue, but the question is if the relatively small cost of adding a bit too jmp_buf makes it worth it, as long as people understand that there is no fp support in klibc. Thorsten Glaser <tg at mirbsd.de> wrote:>Steve Capper dixit: > >>> Do we need the fpregs saved even though klibc doesn't do fp? > >>For gcc targetting Aarch64, We can only guarantee that d8-d15 are >>left alone when -mgeneral-regs-only is supplied for building klibc >>and any software linked against klibc. I would much prefer to > >We can enforce this in klcc, just like -mregparm=3 is used by >the i386 target. > >bye, >//mirabilos-- Sent from my mobile phone. Please pardon brevity and lack of formatting.
On Mon, Nov 11, 2013 at 07:20:04AM -0800, H. Peter Anvin wrote:> Yes, that is not an issue, but the question is if the relatively small cost of adding a bit too jmp_buf makes it worth it, as long as people understand that there is no fp support in klibc. > > Thorsten Glaser <tg at mirbsd.de> wrote: > >Steve Capper dixit: > > > >>> Do we need the fpregs saved even though klibc doesn't do fp? > > > >>For gcc targetting Aarch64, We can only guarantee that d8-d15 are > >>left alone when -mgeneral-regs-only is supplied for building klibc > >>and any software linked against klibc. I would much prefer to > > > >We can enforce this in klcc, just like -mregparm=3 is used by > >the i386 target. > > > >bye, > >//mirabilosI've added -mgeneral-regs-only to KLIBCREQFLAGS (and some comments and code changes in pertinent places), and this has made it into the klcc wrapper. Thanks, -- Steve