From: Stafford Horne <shorne@gmail.com>
To: Gary Lau <zgliu@foxmail.com>
Cc: linux-openrisc <linux-openrisc@vger.kernel.org>
Subject: Re: [QUESTION] Does or1k-elf-gcc handle OpenRISC 4B alignmentrequirement?
Date: Mon, 14 Jul 2025 15:59:19 +0100 [thread overview]
Message-ID: <aHUbRxBk6fBnLaj3@antec> (raw)
In-Reply-To: <tencent_FEB56C143F39CEE7BB1C5B3A1C7E82940909@qq.com>
On Mon, Jul 14, 2025 at 05:21:16PM +0800, Gary Lau wrote:
> Hi Stafford,
> The load elf failure seems not be related to the alignment issue.
> It seems be related to the memory stack conflict between main program and client elf.
> I will fix it.
OK Great.
> Anyway, thanks that you confirmed the or1k-gcc does not take care of 4B alignment.
Thanks for confirming.
-Stafford
prev parent reply other threads:[~2025-07-14 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 6:20 [QUESTION] Does or1k-elf-gcc handle OpenRISC 4B alignment requirement? 48494605
2025-07-12 10:14 ` Stafford Horne
[not found] ` <tencent_FEB56C143F39CEE7BB1C5B3A1C7E82940909@qq.com>
2025-07-14 14:59 ` Stafford Horne [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=aHUbRxBk6fBnLaj3@antec \
--to=shorne@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
--cc=zgliu@foxmail.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).