From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: will schmidt <will_schmidt@vnet.ibm.com>,
Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH], Make PowerPC -mcpu=future enable -mpcrel on linux ELFv2
Date: Wed, 1 Apr 2020 15:16:52 -0400 [thread overview]
Message-ID: <20200401191652.GA12337@ibm-tinman.the-meissners.org> (raw)
In-Reply-To: <20200330225149.GU22482@gate.crashing.org>
On Mon, Mar 30, 2020 at 05:51:49PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Mar 30, 2020 at 12:50:43PM -0500, will schmidt wrote:
> > On Fri, 2020-03-27 at 21:31 -0400, Michael Meissner via Gcc-patches
> > > * config/rs6000/rs6000.c (PCREL_SUPPORTED_BY_OS): New macro.
> > > (rs6000_option_override_internal): Set the -mprefixed and
> > > -mpcrel
> > > options for -mcpu=future if these options can be used.
> > >
> > s/can be used/are supported by the platform/ ?
>
> The code says
> /* Enable -mprefixed by default on 64-bit 'future' systems. */
> /* If the OS has support for PC-relative relocations, enable it now. */
> and something like that should go in the changelog as well (two lines in
> changelog is fine -- they are two hunks of patch as well, anyway!)
Ok.
> > > +/* Enable default support for PC-relative addressing on the 'future'
> > > system if
> > > + we can use the PC-relative instructions. Currently this support
> > > only exits
> >
> > exists
> >
> > > + for the ELF v2 object file format using the medium code
> > > model. */
> >
> > should that be "s/object file format/ABI/" ?
>
> Yes.
Ok.
> > > -/* Support for a future processor's features. Do not enable -mpcrel
> > > until it
> > > - is fully functional. */
> > > +/* Support for a future processor's features. We do not set -mpcrel
> > > or
> > > + -mprefixed here. These bits are set in rs6000_option_override if
> > > the system
> > > + supports those options. */
> >
> > I'm still not sure the comment here is actually necessary, there are
> > many other places where we also do not set -mpcrel or -mprefixed. If
> > history of the code here requires a hint to point at those options
> > being set in rs6000_option_override, then it's fine.
>
> If you really need to say you do *not* do something, you should say why
> not. Without that it only leaves more questions to the reader :-)
>
> Hopefully that then also explains why the reader should care about this.
Given this comment is against Will's comment, and not the original code, is
there anything I need to do to the code (other than the ChangeLog and adjusting
object file format to ABI?
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2020-04-01 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 1:31 Michael Meissner
2020-03-30 17:50 ` will schmidt
2020-03-30 22:51 ` Segher Boessenkool
2020-04-01 19:16 ` Michael Meissner [this message]
2020-04-01 21:36 ` Segher Boessenkool
2020-04-01 23:11 ` Michael Meissner
2020-04-02 19:27 ` Segher Boessenkool
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=20200401191652.GA12337@ibm-tinman.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.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).