public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>,
	Richard Henderson <rth@twiddle.net>,
	Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH v2 0/2] OpenRISC support for cmodel=large
Date: Sun, 15 Aug 2021 07:25:05 +0900	[thread overview]
Message-ID: <YRhCwQPveo8+lnGH@antec> (raw)
In-Reply-To: <9e4b2d98-5ba1-c35f-b419-3df2d84a5dab@benettiengineering.com>

On Sun, Aug 15, 2021 at 12:05:37AM +0200, Giulio Benetti wrote:
> On 8/15/21 12:03 AM, Stafford Horne wrote:
> > On Sat, Aug 14, 2021 at 11:01:16PM +0200, Giulio Benetti wrote:
> > > Hi All,
> > > 
> > > On 5/1/21 11:11 PM, Stafford Horne wrote:
> > > > 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
> > > > 
> > > 
> > > I've tested this patchset and works as expected.
> > > It fixed libgeos build failure in conjunction with:
> > > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3c3de29b048bca6b4aa4235c647b9328e71801b6
> > > 
> > > Hope this helps to commit it upstream since I still don't see it, or am I
> > > wrong?
> > 
> > You are not wrong, I did not push the changed to GCC yet.  I will do soon.
> 
> Ah ok, you're the maintainer :-) I thought there was someone else who needed
> to push it :-)

Yeah, I pushed it now.

  reply	other threads:[~2021-08-14 22:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 21:11 Stafford Horne
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 [this message]
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=YRhCwQPveo8+lnGH@antec \
    --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).