All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 3/4] arm: remove outdated comment concerning -ffixed-x18
Date: Wed, 27 May 2020 20:04:23 +0200	[thread overview]
Message-ID: <20200527180424.39395-4-xypron.glpk@gmx.de> (raw)
In-Reply-To: <20200527180424.39395-1-xypron.glpk@gmx.de>

Clang 9 supports -ffixed-x18.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
---
 arch/arm/include/asm/global_data.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/arch/arm/include/asm/global_data.h b/arch/arm/include/asm/global_data.h
index 7c0905d240..2aafc6d206 100644
--- a/arch/arm/include/asm/global_data.h
+++ b/arch/arm/include/asm/global_data.h
@@ -96,10 +96,6 @@ static inline gd_t *get_gd(void)
 	gd_t *gd_ptr;

 #ifdef CONFIG_ARM64
-	/*
-	 * Make will already error that reserving x18 is not supported at the
-	 * time of writing, clang: error: unknown argument: '-ffixed-x18'
-	 */
 	__asm__ volatile("mov %0, x18\n" : "=r" (gd_ptr));
 #else
 	__asm__ volatile("mov %0, r9\n" : "=r" (gd_ptr));
--
2.26.2

  parent reply	other threads:[~2020-05-27 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 18:04 [PATCH 0/4] arm: fix clang build errors Heinrich Schuchardt
2020-05-27 18:04 ` [PATCH 1/4] efi_loader: allow compiling with clang Heinrich Schuchardt
2020-05-31 14:08   ` Simon Glass
2020-05-27 18:04 ` [PATCH 2/4] trace: clang compatible handling of gd register Heinrich Schuchardt
2020-05-31 14:08   ` Simon Glass
2020-07-08  3:03   ` Tom Rini
2020-05-27 18:04 ` Heinrich Schuchardt [this message]
2020-05-31 14:08   ` [PATCH 3/4] arm: remove outdated comment concerning -ffixed-x18 Simon Glass
2020-07-08  3:03   ` Tom Rini
2020-05-27 18:04 ` [PATCH 4/4] arm: use correct argument size of special registers Heinrich Schuchardt
2020-07-08  3:03   ` Tom Rini
2020-06-14 15:51 ` [PATCH 0/4] arm: fix clang build errors Heinrich Schuchardt
2020-06-14 15:59   ` 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=20200527180424.39395-4-xypron.glpk@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.