[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SH4 port
From: |
Paulo César Pereira de Andrade |
Subject: |
Re: SH4 port |
Date: |
Tue, 3 Sep 2024 12:27:47 -0300 |
Em ter., 3 de set. de 2024 às 11:46, Paul Cercueil
<paul@crapouillou.net> escreveu:
>
> Hi Paulo,
Hi Paul,
> I see you're active :)
>
> Can we merge the SH4 code?
>
> I just need to know how to generate the sh-sz.c file, if it's
> generated.
>
> Cheers,
> -Paul
>
>
> Le samedi 13 juillet 2024 à 01:54 +0200, Paul Cercueil a écrit :
> > Hi Paulo,
> >
> > I have 79/79 tests passing now with my SH4 port!
> >
> > I had to use a few tricks to support floating-point; notably I switch
> > to the second bank of 16 FPR in the function prolog, so that the
> > function arguments are always in the bank; this means all 16 FPR can
> > be
> > used by Lightning (as 8 32/64-bit FPR).
> >
> > It's not clear to me whether or not the banked registers are callee-
> > saved, I could not find that info anywhere. But they are used really
> > seldomly (I think only in hand-written ASM) so it should be fine.
> >
> > Before I send a PR I need to update my sz.c file. I wonder if there
> > is
> > an automated way to generate it? Or am I supposed to update it by
> > hand?
To generate the -sz.c file run:
$ ./configure $OPTS --enable-devel-get-jit-size
$ make $OPTS get_jit_size
During make check it will collect how many bytes were used to
generate machine code in a temporary file. The size command will
read the temporary file and generate in the toplevel the -sz.c file.
It is a simple/hacky rule, see Makefile.am:
"""
get_jit_size:: $(JIT_SIZE_PATH)
$(JIT_SIZE_PATH):
make clean
make check
$(top_builddir)/size
""
> > Cheers,
> > -Paul
Thanks!
Paulo
- Re: SH4 port, Paul Cercueil, 2024/09/03
- Re: SH4 port,
Paulo César Pereira de Andrade <=