From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@imgtec.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: dec: Avoid la pseudo-instruction in delay slots
Date: Mon, 3 Oct 2016 01:21:41 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.20.1609210301430.19345@eddie.linux-mips.org> (raw)
In-Reply-To: <20160920123301.GN5881@linux-mips.org>
On Tue, 20 Sep 2016, Ralf Baechle wrote:
> > I take it it's a quest for a clean compilation with no warnings reported,
> > as the message is otherwise harmless and correct code is produced here.
> >
> > Some of the systems affected are not necessarily fast (e.g. clocked at
> > 12MHz), so I wonder if we shouldn't just bite the bullet and expand the
> > %hi/%lo pair here. Even with R4k DECstations we only support `-msym32'
> > compilation only, due to R4k errata, so it's not like the higher parts
> > will ever be needed for address calculation.
> >
> > Alternatively we could have a `.set warn'/`.set nowarn' setting in GAS,
> > previously discussed I believe, although it would take a bit to propagate.
>
> Yeah, I'm already looking into the other direction whenever this warning
> pops up - and it does so often. I've even pondered submitting something
> like -Werror for gas ;-)
Well, the GCC driver already handles it and catches warnings from GAS if
requested, doesn't it?
> It's not very elegant but you could just open code everything, see below
> patch. Compiles but not runtime tested due to lack of hardware.
That's what I noted above and as also noted you only need the %hi/%lo
variant due to the `-msym32' restriction for 64-bit DECstation kernels;
the kernel is always linked to KSEG0.
Alternatively for maximum safety perhaps we could define PTR_LA_EXPLICIT
or suchlike with a suitable open-coded sequence for the pointer width
chosen; note however that `-msym32' doesn't set any CPP's internal
predefined macro, so we'd have to define our own to control this.
> Maciej, can you test this?
I'll see what I can do; I've been travelling a lot lately.
Maciej
prev parent reply other threads:[~2016-10-03 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 14:19 Paul Burton
2016-09-19 22:30 ` Maciej W. Rozycki
2016-09-20 12:33 ` Ralf Baechle
2016-10-03 0:21 ` 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.20.1609210301430.19345@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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
Powered by JetHome