From: Rich Felker <dalias@libc.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Reviving SH FDPIC target
Date: Thu, 03 Sep 2015 04:33:00 -0000 [thread overview]
Message-ID: <20150903005101.GN17773@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150902210535.GM17773@brightrain.aerifal.cx>
On Wed, Sep 02, 2015 at 05:05:35PM -0400, Rich Felker wrote:
> On Wed, Sep 02, 2015 at 07:59:45PM +0000, Joseph Myers wrote:
> > On Wed, 2 Sep 2015, Rich Felker wrote:
> >
> > > Also, according to Joseph Myers, there was some unresolved
> > > disagreement that stalled (and eventually sunk) the old patch, so if
> > > anyone's still around who has objections to it, could you speak up and
> > > let me know what's wrong? Kaz Kojima seems to have approved the patch
> > > at the time so I'm confused what the issue was/is.
> >
> > It's patch 1/3 (architecture-independent) that had the disagreement (and
> > patch 3/3 depends on patch 1/3).
> >
> > https://gcc.gnu.org/ml/gcc-patches/2010-08/msg01462.html
>
> So this is only for __fpscr_values? In that case I think the right
> solution is just to follow up with getting rid of __fpscr_values, if
> it's not already done:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60138
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53513
>
> 53513 is marked fixed, but I didn't follow up to confirm that the
> actual problems I reported in 60138 are fixed; I'll do some more
> research on this. But if all goes well, we can just drop 1/3.
I've confirmed that gcc 5.2 does not produce references to
__fpscr_values; instead, it does:
mov.l .L4,r3
...
sts fpscr,r1
xor r3,r1
lds r1,fpscr
...
.L4:
.long 524288
So if __fpscr_values was the only reason for patch 1/3 in the FDPIC
patchset, I think we can safely drop it. And patch 2/3 was already
committed, so 3/3, the one I was originally looking at, seems to be
all we need. It was approved at the time, so I'll proceed with merging
it with 5.2.0.
Rich
next prev parent reply other threads:[~2015-09-03 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 18:36 Rich Felker
2015-09-02 20:00 ` Joseph Myers
2015-09-02 21:14 ` Rich Felker
2015-09-03 4:33 ` Rich Felker [this message]
2015-09-03 14:59 ` Joseph Myers
2015-09-03 15:59 ` Rich Felker
2015-09-04 20:22 ` Rich Felker
2015-09-04 23:08 ` Segher Boessenkool
2015-09-05 12:37 ` Rich Felker
2015-09-13 17:11 ` Rich Felker
2015-09-11 4:05 ` Rich Felker
2015-09-11 8:02 ` Rich Felker
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=20150903005101.GN17773@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).