From: "Alex Bennée" <alex.bennee@linaro.org>
To: Brian Cain <bcain@quicinc.com>
Cc: Taylor Simpson <tsimpson@quicinc.com>,
Richard Henderson <richard.henderson@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: hexagon container update
Date: Mon, 17 Jan 2022 14:47:21 +0000 [thread overview]
Message-ID: <87o84aa03n.fsf@linaro.org> (raw)
In-Reply-To: <SN6PR02MB42050D02581C5FF732732D29B8559@SN6PR02MB4205.namprd02.prod.outlook.com>
Brian Cain <bcain@quicinc.com> writes:
>> -----Original Message-----
>> From: Brian Cain
>> Sent: Friday, October 1, 2021 7:23 PM
>> To: Richard Henderson <richard.henderson@linaro.org>; Alex Bennée
>> <alex.bennee@linaro.org>; qemu-devel@nongnu.org
>> Cc: Taylor Simpson <tsimpson@quicinc.com>
>> Subject: RE: hexagon container update
>>
>> > -----Original Message-----
>> > From: Brian Cain
>> ...
>> > > -----Original Message-----
>> > > From: Richard Henderson <richard.henderson@linaro.org>
>> > ...
>> > > On 10/1/21 12:59 PM, Brian Cain wrote:
>> > > > Alex,
>> > > >
>> > > > We need to update the docker container used for hexagon for new test
>> > cases
>> > > proposed in Taylor's recent patch series under review. Thankfully,
>> > CodeLinaro
>> > > has provided a binary of the hexagon cross toolchain so now I think we can
>> > > simplify the hexagon docker file to something like the below. I hope this
>> also
>> > > means that we can remove the exceptional handling for the hexagon
>> > container.
>
> We had some issues with the previous attempt to update the container.
> The linux-user "signals" test failed. Richard pointed out that the
> archive of the C library had what looks like a defect that would cause
> the test to fail.
>
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg849635.html
>
> I'm following up now with a workaround - the attached patch references
> a toolchain which avoids the problem and passes the signals test. This
> toolchain is based on llvm+clang 13.0.1-rc2. BTW, the release page has
> a signature provided in case anyone wants to verify the download:
> https://github.com/quic/toolchain_for_hexagon/releases/tag/13.0.1-rc2_
>
> Can we try again with this new container definition?
>
> -Brian
>
> [2. 0001-Update-Hexagon-toolchain-to-13.0.1-rc2.patch --- text/x-diff; 0001-Update-Hexagon-toolchain-to-13.0.1-rc2.patch]...
Could you send the updated patch against the current master in the usual
way please?
That way I know it's been tested and there is less risk of me botching
up a franken patch by applying to the wrong base.
--
Alex Bennée
next prev parent reply other threads:[~2022-01-17 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 16:59 hexagon container update Brian Cain
2021-10-01 17:23 ` Richard Henderson
2021-10-01 17:59 ` Brian Cain
2021-10-01 21:44 ` Alex Bennée
2021-10-02 0:22 ` Brian Cain
2022-01-15 3:36 ` Brian Cain
2022-01-17 14:47 ` Alex Bennée [this message]
2022-01-18 15:25 ` Brian Cain
2022-01-18 15:41 ` Brian Cain
2021-10-02 13:09 ` Richard Henderson
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=87o84aa03n.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bcain@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=tsimpson@quicinc.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 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).