From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: Re: [PATCH v2] tests/docker: Use binaries for debian-tricore-cross
Date: Wed, 8 Feb 2023 10:03:37 +0100 [thread overview]
Message-ID: <0b9c1ec2-88f6-414b-43e7-fc458fa048c0@linaro.org> (raw)
In-Reply-To: <20230208084859.1195555-1-kbastian@mail.uni-paderborn.de>
On 8/2/23 09:48, Bastian Koppelmann wrote:
> since binutils is pretty old, it fails our CI repeatedly during the
> compilation of tricore-binutils. We created a precompiled version using
> the debian docker image and download it instead of building it ourself.
>
> We also updated the package to include a newer version of binutils, gcc,
> and newlib. The default TriCore ISA version used by tricore-as changed
> from the old version, so we have to specify it now. If we don't
> 'test_fadd' fails with 'unknown opcode'.
>
> Signed-off-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
> ---
> v1 -> v2:
> - Reverted package removal
> - Use updated tricore toolchain that contains gcc and newlib as well
> - updated LD/AS flags in tests/tcg/tricore, as the new binutils would fail
> tests.
>
> tests/docker/dockerfiles/debian-tricore-cross.docker | 10 +++-------
> tests/tcg/tricore/Makefile.softmmu-target | 4 ++--
> 2 files changed, 5 insertions(+), 9 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2023-02-08 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 8:48 [PATCH v2] tests/docker: Use binaries for debian-tricore-cross Bastian Koppelmann
2023-02-08 9:03 ` Philippe Mathieu-Daudé [this message]
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=0b9c1ec2-88f6-414b-43e7-fc458fa048c0@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).