From: "Tom Turelinckx" <tom-HiypchcOusz53ZRCpReHOg@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bus error on sparc64 running type-preservation test
Date: Tue, 14 Apr 2020 18:34:24 +0200 [thread overview]
Message-ID: <4c0be4b4-7f6e-4612-af7b-dfffb400597a@www.fastmail.com> (raw)
In-Reply-To: <20200414062534.GL48061-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
Hi,
On Tue, Apr 14, 2020, at 8:25 AM, David Gibson wrote:
> I've just merged and pushed a change which I think will fix this to
> the master branch. Could you build and test that please?
It seems to work, thanks!
I've verified on debian sparc64 that make and make check succeed when I checkout b28464a, while make check fails with bus error when I checkout 87a656a.
I've also verified that the debian src package version 1.6.0-1 builds successfully on sparc64 with patch b28464a applied locally, and that the same package with the same patch applied still builds successfully on amd64. Those are the only archs I have access to.
> If you can make a minimal testcase which triggers this problem and
> submit it as an addition to the dtc testsuite, that would be terrific.
I have limited experience with C development, and zero experience with alignment issues, DTC or its test suite, so I can't be of much help here...
Best regards,
Tom
next prev parent reply other threads:[~2020-04-14 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 16:09 bus error on sparc64 running type-preservation test Tom Turelinckx
2020-04-13 16:29 ` Tom Turelinckx
2020-04-14 6:25 ` David Gibson
[not found] ` <20200414062534.GL48061-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2020-04-14 16:34 ` Tom Turelinckx [this message]
[not found] ` <4c0be4b4-7f6e-4612-af7b-dfffb400597a-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2020-04-21 3:22 ` David Gibson
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=4c0be4b4-7f6e-4612-af7b-dfffb400597a@www.fastmail.com \
--to=tom-hiypchcousz53zrcprehog@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).