From: Zack Weinberg <zackw@panix.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH] uapi/linux/a.out.h: don't use deprecated system-specific predefines.
Date: Thu, 1 Jun 2017 17:00:45 -0400 [thread overview]
Message-ID: <20170601210045.8638-1-zackw@panix.com> (raw)
uapi/linux/a.out.h uses a number of predefined macros that are
deprecated because they're in the application namespace
(e.g. '#ifdef linux' instead of '#ifdef __linux__').
This patch corrects all of them.
The primary reason this is worth bothering to fix, considering how
obsolete a.out binary support is, is that the GCC build process
considers this such a severe error that it will copy the header into a
private directory and change the macro names, which causes future
updates to the header to be masked. This header probably doesn't get
updated very often anymore, but it is the _only_ uapi header that gets
this treatment, so IMHO it is worth patching just to drive that number
all the way to zero.
Signed-off-by: Zack Weinberg <zackw@panix.com>
---
include/uapi/linux/a.out.h | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/uapi/linux/a.out.h b/include/uapi/linux/a.out.h
index 7caf44c7fa51..e163133cf1b0 100644
--- a/include/uapi/linux/a.out.h
+++ b/include/uapi/linux/a.out.h
@@ -115,21 +115,21 @@ enum machine_type {
/* Address of data segment in memory after it is loaded.
Note that it is up to you to define SEGMENT_SIZE
on machines not listed here. */
-#if defined(vax) || defined(hp300) || defined(pyr)
+#if defined(__vax__) || defined(__hp300__) || defined(__pyr__)
#define SEGMENT_SIZE page_size
#endif
-#ifdef sony
+#ifdef __sony__
#define SEGMENT_SIZE 0x2000
#endif /* Sony. */
-#ifdef is68k
+#ifdef __is68k__
#define SEGMENT_SIZE 0x20000
#endif
-#if defined(m68k) && defined(PORTAR)
+#if defined(__m68k__) && defined(__PORTAR__)
#define PAGE_SIZE 0x400
#define SEGMENT_SIZE PAGE_SIZE
#endif
-#ifdef linux
+#ifdef __linux__
#ifndef __KERNEL__
#include <unistd.h>
#endif
@@ -260,7 +260,7 @@ struct relocation_info
unsigned int r_extern:1;
/* Four bits that aren't used, but when writing an object file
it is desirable to clear them. */
-#ifdef NS32K
+#ifdef __NS32K__
unsigned r_bsr:1;
unsigned r_disp:1;
unsigned r_pad:2;
--
2.11.0
next reply other threads:[~2017-06-01 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 21:00 Zack Weinberg [this message]
2017-06-02 7:10 ` Christoph Hellwig
2017-06-02 12:06 ` Zack Weinberg
2017-06-02 19:12 ` Linus Torvalds
2017-06-14 12:43 ` Zack Weinberg
2017-06-14 15:14 ` Christoph Hellwig
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=20170601210045.8638-1-zackw@panix.com \
--to=zackw@panix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®