public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Stafford Horne <shorne@gmail.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: Wed, 5 May 2021 09:51:43 +0200	[thread overview]
Message-ID: <0E376E20-5570-4914-A816-679D77FB1E24@benettiengineering.com> (raw)
In-Reply-To: <20210505063004.GT3288043@lianli.shorne-pla.net>

Hi Stafford, All,

> Il giorno 5 mag 2021, alle ore 08:30, Stafford Horne <shorne@gmail.com> ha scritto:
> 
> On Mon, May 03, 2021 at 12:34:22PM +0200, Giulio Benetti wrote:
>> Hi Stafford, All,
>> 
>> I've backported this patchset for Buildroot to versions:
>> - 9.3.0
>> - 10.3.0
>> 
>> Does it make sense to send them? I don't know if those version will have
>> minor versions where these backported patches can be applied.
> 
> Do you mean for me/you to send the backported GCC patches for GCC or buildroot?
I mean for GCC, I’ve already sent them for buildroot:
https://patchwork.ozlabs.org/project/buildroot/list/?series=241844

> 
> I don't need backported versions of the toolchains and usually work off the
> latest release/master.  If someone wants them let me know.
I was asking to know if newer minor versions of
binutils and gcc will be released. If yes I could
send your back ported patches here in the 2 mailing lists(binutils and gcc ones).

Giulio Benetti

> 
> -Stafford
> 
>> Best regards
>> -- 
>> Giulio Benetti
>> Benetti Engineering sas
>> 
>>> 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
>>> 

  reply	other threads:[~2021-05-05  7:51 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 [this message]
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=0E376E20-5570-4914-A816-679D77FB1E24@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=openrisc@lists.librecores.org \
    --cc=rth@twiddle.net \
    --cc=shorne@gmail.com \
    /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).