public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.ibm.com>,
	will schmidt <will_schmidt@vnet.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 16:36:05 -0500	[thread overview]
Message-ID: <20200401213605.GB26902@gate.crashing.org> (raw)
In-Reply-To: <20200401191652.GA12337@ibm-tinman.the-meissners.org>

On Wed, Apr 01, 2020 at 03:16:52PM -0400, Michael Meissner wrote:
> > > > -/* 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?

I am agreeing with Will's comment here, just expanding on it.  This
comment isn't helpful (maybe it would be with more provided context,
but as it is, it is not).


Segher

  reply	other threads:[~2020-04-01 21:36 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
2020-04-01 21:36       ` Segher Boessenkool [this message]
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=20200401213605.GB26902@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@linux.ibm.com \
    --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).