From: Alistair Francis <alistair23@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"Maciej W. Rozycki" <macro@wdc.com>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Problem with RISC-V
Date: Sat, 12 Sep 2020 14:49:06 -0700 [thread overview]
Message-ID: <CAKmqyKNW5a7bLDKcdAZS-XpN-kMCtcr9rRgV_tgsYGo1WGFzLQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2009082025080.8874@digraph.polyomino.org.uk>
On Tue, Sep 8, 2020 at 1:25 PM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Tue, 8 Sep 2020, Alistair Francis wrote:
>
> > > choices for RV32 that should be investigated. But when libgcc functions
> > > reference libc functions, those generally need to be listed in
> > > localplt.data for that glibc configuration (with a '?' to make the
> > > reference optional, see e.g. the
> > > sysdeps/unix/sysv/linux/powerpc/powerpc32/nofpu/localplt.data entries for
> >
> > I sent a patch to do exactly that, but it was never accepted. Should I
> > look at merging it?
>
> Yes.
Ok.
I bisected GCC, and apparently the bad commit is this:
commit 68ec60c4a377b532ec2d265ea542107c36b1d15c (HEAD, tag:
basepoints/gcc-10, refs/bisect/bad)
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Apr 25 20:01:17 2019 +0200
* BASE-VER: Set to 10.0.0.
From-SVN: r270581
diff --git a/gcc/BASE-VER b/gcc/BASE-VER
index 37ad5c8b19d..a13e7b9c87e 100644
--- a/gcc/BASE-VER
+++ b/gcc/BASE-VER
@@ -1 +1 @@
-9.0.1
+10.0.0
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 0682a44cd4a..fcdbfe4caec 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2019-04-25 Jakub Jelinek <jakub@redhat.com>
+
+ * BASE-VER: Set to 10.0.0.
+
2019-04-25 Richard Biener <rguenther@suse.de>
PR middle-end/89765
I have no idea why though.
Alistair
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
prev parent reply other threads:[~2020-09-12 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 13:11 Lukasz Majewski
2020-09-07 13:29 ` Adhemerval Zanella
2020-09-07 15:22 ` Alistair Francis
2020-09-07 16:52 ` Joseph Myers
2020-09-08 15:57 ` Joseph Myers
2020-09-08 16:02 ` H.J. Lu
2020-09-08 16:39 ` Joseph Myers
2020-09-08 19:47 ` Alistair Francis
2020-09-08 20:25 ` Joseph Myers
2020-09-12 21:49 ` Alistair Francis [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=CAKmqyKNW5a7bLDKcdAZS-XpN-kMCtcr9rRgV_tgsYGo1WGFzLQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@wdc.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).