[PATCH] libffi: Fix MIPS r6 support

YunQiang Su syq@debian.org
Tue Aug 31 02:46:21 GMT 2021


Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> 于2021年8月30日周一 下午9:48写道:
>
>
>
> On 8/30/2021 2:47 AM, YunQiang Su wrote:
> > 在 2021/8/30 5:00, Jeff Law 写道:
> >>
> >>
> >> On 8/28/2021 1:23 AM, Xi Ruoyao wrote:
> >>> On Fri, 2021-08-27 at 15:28 -0600, Jeff Law via Gcc-patches wrote:
> >>>>
> >>>> On 8/26/2021 10:58 PM, YunQiang Su wrote:
> >>>>> for some instructions, MIPS r6 uses different encoding other than
> >>>>> the previous releases.
> >>>>>
> >>>>> 1. mips/n32.S disable .set mips4: since it casuses old insn encoding
> >>>>>      is used.
> >>>>>      https://github.com/libffi/libffi/pull/396
> >>>>> 2. mips/ffi.c: the encoding for JR is hardcoded: we need to use
> >>>>>      different value for r6 and pre-r6.
> >>>>>      https://github.com/libffi/libffi/pull/401
> >>>>>
> >>>>> libffi/
> >>>>>          PR libffi/83636
> >>>>>          * src/mips/n32.S: disable .set mips4
> >>>>>          * src/mips/ffi.c: use different JR encoding for r6.
> >>>> These should go to the upstream libffi project.  Once accepted there
> >>>> you
> >>>> can add them to GCC.
> >>> Hi Jeff,
> >>>
> >>> The two PRs are already merged, and released since libffi-3.3.0 (now
> >>> the
> >>> upstream latest release is 3.4.2).
> >> ACK.  Thanks for confirming.  It's always OK to cherrypick/backport
> >> from libffi back to GCC.
> >>
> >>>
> >>> I don't have a MIPSr6 so I can't test though.
> >> Understood.   Me neither, but I really should get a tiny chroot for
> >> mipsr6 so that my tester can validate it regularly.
> >>
> >
> > We have port Debian to MIPS64r6el.
> > http://58.246.137.130:20180/tools/tarball/
> > You can use both buster(Debian 10) or bullseye (Debian 11).
> >
> > And both qemu-system and qemu-user can work.
> Understood.  I need the minimal chroot to compress down under 100M to

A minimal tarball is ready now with size about 87M.

> make gitlab happy (that's where my scripts & jenkins system expect to
> find them).  My scripts to build the chroots also ensure a consistent
> set of packages & version #s across the different systems being
> tested.   I've just never gotten around to building one for mips64r6.  I
> could probably take yours trim out unnecessary stuff and use it for
> now.  Getting a bootstrap test on the target weekly is definitely helpful.
>

That's great.
Since the minimal rootfs lacks of lots of tools, and
if you need some tools, you can just apt install them,then.

> jeff


More information about the Gcc-patches mailing list