u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: "kleines Filmröllchen" <malu.bertsch@gmail.com>
To: u-boot@lists.denx.de
Cc: "kleines Filmröllchen" <filmroellchen@serenityos.org>,
	"Bin Meng" <bmeng@tinylab.org>, Leo <ycliang@andestech.com>,
	"Rick Chen" <rick@andestech.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Tom Rini" <trini@konsulko.com>
Subject: [PATCH 0/1] riscv: Support building with Clang
Date: Sat, 20 Jan 2024 01:14:03 +0100	[thread overview]
Message-ID: <20240120001405.29294-1-filmroellchen@serenityos.org> (raw)


Hello everyone!

This is a minimal patchset for making U-Boot build with Clang on RISC-V,
something I stumbled upon while writing U-Boot build scripts for
SerenityOS's RISC-V port. The only change is a (for unclear reasons...)
differently-named flag for fixing the global pointer.

Notably, this patch does not make U-Boot actually functional under
Clang. Booting this on QEMU (`-M virt -kernel path/to/u-boot -serial
stdio`) hangs after the image is loaded. I do not have the motivation to
debug this, but it may be helpful for further work on getting a working
build out of Clang on this architecture.

Greetings,
kleines Filmröllchen

PS: I am new to a mail patch contribution workflow and may have messed
this up despite reading through plenty relevant documentation. Please
kindly point out any improvements I could make on my side.


kleines Filmröllchen (1):
  riscv: Support building with Clang

 arch/riscv/config.mk | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

-- 
2.39.2

             reply	other threads:[~2024-01-20  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20  0:14 kleines Filmröllchen [this message]
2024-01-20  0:14 ` [PATCH 1/1] riscv: Support building with Clang kleines Filmröllchen
2024-01-20  0:20   ` Tom Rini
2024-01-25 14:06     ` [PATCH v2 0/1] " kleines Filmröllchen
2024-01-25 14:06       ` [PATCH v2 1/1] " kleines Filmröllchen
2024-01-25 14:16         ` Tom Rini

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=20240120001405.29294-1-filmroellchen@serenityos.org \
    --to=malu.bertsch@gmail.com \
    --cc=bmeng@tinylab.org \
    --cc=filmroellchen@serenityos.org \
    --cc=rick@andestech.com \
    --cc=samuel@sholland.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.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).