public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Jim Wilson <jimw@sifive.com>
Cc: Kito Cheng <kito.cheng@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 Andrew Waterman <andrew@sifive.com>,
	 Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] RISC-V/libgcc: Use `-fasynchronous-unwind-tables' for LIB2_DIVMOD_FUNCS
Date: Tue, 29 Sep 2020 01:26:20 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2009290108220.61083@eddie.linux-mips.org> (raw)
In-Reply-To: <CAFyWVaa0d8LMeVAZsxgT339SSXzPyx-pfvAsyFO5WJsSpRaQ0Q@mail.gmail.com>

Hi Jim,

> On Sun, Aug 30, 2020 at 11:39 PM Kito Cheng <kito.cheng@gmail.com> wrote
> > Hi Maciej:
> > LGTM, thanks for your patch!
> 
> I don't see this patch in the FSF GCC tree.  Maciej are you going to
> commit it?  Or do you want us to commit it for you?

 Since my departure from WDC I have been largely away, travelling and 
doing all kinds of personal stuff.  I hoped someone would pick it up and 
make some progress with the generic change I proposed earlier:

<https://gcc.gnu.org/pipermail/gcc-patches/2020-August/552327.html>

which would make the RISC-V-specific hack redundant, but clearly no one 
could be bothered enough.  I have pushed this change then so as not to 
hinder RISC-V support in GCC.

 Thanks, Kito, for your review!

  Maciej

      reply	other threads:[~2020-09-29  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 13:18 Maciej W. Rozycki
2020-08-31  6:38 ` Kito Cheng
2020-09-28 19:38   ` Jim Wilson
2020-09-29  0:26     ` Maciej W. Rozycki [this message]

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=alpine.LFD.2.21.2009290108220.61083@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jimw@sifive.com \
    --cc=kito.cheng@gmail.com \
    --cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).