From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/criu: disable mips
Date: Sat, 13 Jan 2024 23:54:06 +0100 [thread overview]
Message-ID: <87a5p8n8tt.fsf@48ers.dk> (raw)
In-Reply-To: <878r4trn90.fsf@48ers.dk> (Peter Korsgaard's message of "Sat, 13 Jan 2024 21:28:59 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
>> mips raises the following build failure since the addition of the
>> package in commit 3e4b479f39c15ffdf307ec8395d856680c727204:
>> compel/arch/mips/plugins/std/memcpy.S:7: Error: opcode not supported on this processor: mips32 (mips32) `dadd $2,$0,$4'
>> compel/arch/mips/plugins/std/memcpy.S:8: Error: opcode not supported on this processor: mips32 (mips32) `daddiu $13,$0,0'
>> Indeed, dadd and daddiu are specific to mips64
>> Building on mips64 doesn't work either as it raises the following build
>> failure:
>> /tmp/ccArXSfi.s:305: Error: opcode not supported on this processor: mips64 (mips64) `rdhwr $2,$29'
>> Fixes:
>> - http://autobuild.buildroot.org/results/b0341d0654e66bdac2c91d5949be3810a961d9da
>> - http://autobuild.buildroot.org/results/b7b8860476de04980bd8c7241d3dd5a01a0251c8
>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> Committed to 2023.11.x, thanks.
Sorry, this was supposed to be about the i386 patch instead.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-13 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 19:40 [Buildroot] [PATCH 1/1] package/criu: disable mips Fabrice Fontaine
2024-01-13 20:28 ` Peter Korsgaard
2024-01-13 22:54 ` Peter Korsgaard [this message]
2024-01-13 22:53 ` Peter Korsgaard
2024-01-14 18:29 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5p8n8tt.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=marcus.folkesson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.