From: Stafford Horne <shorne@gmail.com>
To: GCC patches <gcc-patches@gcc.gnu.org>
Cc: Richard Henderson <rth@twiddle.net>,
Openrisc <openrisc@lists.librecores.org>,
giulio.benetti@benettiengineering.com,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH v2 0/2] OpenRISC support for cmodel=large
Date: Sun, 2 May 2021 06:11:43 +0900 [thread overview]
Message-ID: <20210501211145.2980164-1-shorne@gmail.com> (raw)
Changes from v1:
- Added patch to enabled cmodle=large on crtstuff
This series fixes some bugs found when linking large binaries, both in buildroot
and glibc testing.
Stafford Horne (2):
or1k: Add mcmodel option to handle large GOTs
or1k: Use cmodel=large when building crtstuff
gcc/config/or1k/or1k-opts.h | 30 ++++++++++++++++++++++++++++++
gcc/config/or1k/or1k.c | 11 +++++++++--
gcc/config/or1k/or1k.h | 7 +++++++
gcc/config/or1k/or1k.opt | 19 +++++++++++++++++++
gcc/doc/invoke.texi | 12 +++++++++++-
libgcc/config.host | 4 ++--
libgcc/config/or1k/t-crtstuff | 2 ++
7 files changed, 80 insertions(+), 5 deletions(-)
create mode 100644 gcc/config/or1k/or1k-opts.h
create mode 100644 libgcc/config/or1k/t-crtstuff
--
2.26.2
next reply other threads:[~2021-05-01 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 21:11 Stafford Horne [this message]
2021-05-01 21:11 ` [PATCH v2 1/2] or1k: Add mcmodel option to handle large GOTs Stafford Horne
2021-05-01 21:11 ` [PATCH v2 2/2] or1k: Use cmodel=large when building crtstuff Stafford Horne
2021-05-03 10:34 ` [PATCH v2 0/2] OpenRISC support for cmodel=large Giulio Benetti
2021-05-05 6:30 ` Stafford Horne
2021-05-05 7:51 ` Giulio Benetti
2021-08-14 21:01 ` Giulio Benetti
2021-08-14 22:03 ` Stafford Horne
2021-08-14 22:05 ` Giulio Benetti
2021-08-14 22:25 ` Stafford Horne
2021-08-14 22:32 ` Giulio Benetti
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=20210501211145.2980164-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=openrisc@lists.librecores.org \
--cc=rth@twiddle.net \
/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).