From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 4/5] or1k: Add note to indicate execstack
Date: Wed, 20 May 2020 05:37:49 +0900 [thread overview]
Message-ID: <20200519203750.401593-5-shorne@gmail.com> (raw)
In-Reply-To: <20200519203750.401593-1-shorne@gmail.com>
Define TARGET_ASM_FILE_END as file_end_indicate_exec_stack to allow
generation of the ".note.GNU-stack" section note. This allows binutils
to properly set PT_GNU_STACK in the program header.
This fixes a glibc execstack testsuite test failure found while working
on the OpenRISC glibc port.
gcc/ChangeLog:
* config/or1k/linux.h (TARGET_ASM_FILE_END): Define macro.
---
gcc/config/or1k/linux.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/config/or1k/linux.h b/gcc/config/or1k/linux.h
index 21cef067dda..8693e884e2a 100644
--- a/gcc/config/or1k/linux.h
+++ b/gcc/config/or1k/linux.h
@@ -42,4 +42,6 @@
%{!shared:-dynamic-linker " GNU_USER_DYNAMIC_LINKER "}}} \
%{static-pie:-Bstatic -pie --no-dynamic-linker -z text}"
+#define TARGET_ASM_FILE_END file_end_indicate_exec_stack
+
#endif /* GCC_OR1K_LINUX_H */
--
2.26.2
next prev parent reply other threads:[~2020-05-19 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:37 [OpenRISC] [PATCH 0/5] OpenRISC GCC Fixes for Glibc Support Stafford Horne
2020-05-19 20:37 ` [OpenRISC] [PATCH 1/5] or1k: Implement profile hook calling _mcount Stafford Horne
2020-05-19 20:37 ` [OpenRISC] [PATCH 2/5] or1k: Add builtin define to detect hard float Stafford Horne
2020-05-19 20:37 ` [OpenRISC] [PATCH 3/5] or1k: Support for softfloat to emulate hw exceptions Stafford Horne
2020-05-19 20:37 ` Stafford Horne [this message]
2020-05-19 20:37 ` [OpenRISC] [PATCH 5/5] or1k: Fixup exception header data encodings Stafford Horne
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=20200519203750.401593-5-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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 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.