From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] RS6000: Use .machine ppc for some CRT files
Date: Tue, 7 Apr 2020 07:18:25 +0200 [thread overview]
Message-ID: <20200407051825.12516-1-sebastian.huber@embedded-brains.de> (raw)
Since commit e154242724b084380e3221df7c08fcdbd8460674 the flag -many is
sometimes not passed to the assembler. Use .machine ppc to prevent
errors if these files are assembled for an ISA which does not support
FPRs.
libgcc/
* config/rs6000/crtresfpr.S: Use .machine ppc.
* config/rs6000/crtresxfpr.S: Likewise.
* config/rs6000/crtsavfpr.S: Likewise.
---
libgcc/config/rs6000/crtresfpr.S | 1 +
libgcc/config/rs6000/crtresxfpr.S | 1 +
libgcc/config/rs6000/crtsavfpr.S | 1 +
3 files changed, 3 insertions(+)
diff --git a/libgcc/config/rs6000/crtresfpr.S b/libgcc/config/rs6000/crtresfpr.S
index 6c0d01bf9c1..99e6f086026 100644
--- a/libgcc/config/rs6000/crtresfpr.S
+++ b/libgcc/config/rs6000/crtresfpr.S
@@ -27,6 +27,7 @@
/* Do any initializations needed for the eabi environment */
+ .machine ppc
.section ".text"
#include "ppc-asm.h"
diff --git a/libgcc/config/rs6000/crtresxfpr.S b/libgcc/config/rs6000/crtresxfpr.S
index 9f01fa5094b..9931db244f7 100644
--- a/libgcc/config/rs6000/crtresxfpr.S
+++ b/libgcc/config/rs6000/crtresxfpr.S
@@ -27,6 +27,7 @@
/* Do any initializations needed for the eabi environment */
+ .machine ppc
.section ".text"
#include "ppc-asm.h"
diff --git a/libgcc/config/rs6000/crtsavfpr.S b/libgcc/config/rs6000/crtsavfpr.S
index fa043ddd078..dd8743ae058 100644
--- a/libgcc/config/rs6000/crtsavfpr.S
+++ b/libgcc/config/rs6000/crtsavfpr.S
@@ -27,6 +27,7 @@
/* Do any initializations needed for the eabi environment */
+ .machine ppc
.section ".text"
#include "ppc-asm.h"
--
2.16.4
next reply other threads:[~2020-04-07 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 5:18 Sebastian Huber [this message]
2020-04-17 5:59 ` Sebastian Huber
2020-04-24 20:55 ` Segher Boessenkool
2020-04-24 21:47 ` Peter Bergner
2020-04-25 0:15 ` Segher Boessenkool
2020-04-25 0:20 ` Segher Boessenkool
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=20200407051825.12516-1-sebastian.huber@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.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).