From: Jeff Law <jeffreyalaw@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>,
"Kito Cheng" <kito.cheng@gmail.com>,
"Jin Ma" <jinma@linux.alibaba.com>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"richard.sandiford" <richard.sandiford@arm.com>,
"Robin Dapp" <rdapp.gcc@gmail.com>, 钟居哲 <juzhe.zhong@rivai.ai>,
"jinma.contrib" <jinma.contrib@gmail.com>
Subject: Re: [PATCH v2] RISC-V: THEAD: Fix improper immediate value for MODIFY_DISP instruction on 32-bit systems.
Date: Mon, 5 Feb 2024 08:34:48 -0700 [thread overview]
Message-ID: <a4e78da7-9399-4c2e-9268-dc53a9c26d01@gmail.com> (raw)
In-Reply-To: <mvmwmrj54oy.fsf@linux-m68k.org>
On 2/5/24 08:08, Andreas Schwab wrote:
> On Feb 05 2024, Jeff Law wrote:
>
>> Until such systems are common, these niggling issues are bound to show up.
>
> It won't if you do it properly: build with a cross compiler that was
> built from the same source and enable -Werror.
We're all aware you *can* do that. But it's never been a requirement to
commit a patch.
jeff
next prev parent reply other threads:[~2024-02-05 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 9:20 [PATCH] " Jin Ma
2024-01-29 9:23 ` Andrew Pinski
2024-01-29 9:36 ` Jin Ma
2024-01-29 9:57 ` [PATCH v2] " Jin Ma
2024-01-29 12:32 ` Kito Cheng
2024-01-30 6:40 ` Christoph Müllner
2024-02-03 13:11 ` Andreas Schwab
2024-02-05 12:00 ` Christoph Müllner
2024-02-05 14:56 ` Jeff Law
2024-02-05 15:08 ` Andreas Schwab
2024-02-05 15:34 ` Jeff Law [this message]
2024-02-05 15:39 ` Andreas Schwab
2024-02-05 23:23 ` Christoph Müllner
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=a4e78da7-9399-4c2e-9268-dc53a9c26d01@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jinma.contrib@gmail.com \
--cc=jinma@linux.alibaba.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=rdapp.gcc@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=schwab@linux-m68k.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).