From: Michael Meissner <meissner@linux.ibm.com>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Michael Meissner <meissner@linux.ibm.com>
Subject: Re: [PATCH] rs6000: Add basic support for prefixed and PC-relative addresses
Date: Thu, 30 May 2019 23:28:00 -0000 [thread overview]
Message-ID: <20190530215422.GA9844@ibm-toto.the-meissners.org> (raw)
In-Reply-To: <f9118c1a-3443-cb32-fbf8-cc1c16bdd27e@linux.ibm.com>
On Thu, May 30, 2019 at 02:43:49PM -0500, Bill Schmidt wrote:
> On 5/30/19 2:20 PM, Segher Boessenkool wrote:
> > On Wed, May 29, 2019 at 10:49:35PM -0500, Bill Schmidt wrote:
> >> * config/rs6000/predicates.md (pcrel_address): New
> >> define_predicate.
> > Please put that on one line?
>
> OK. Emacs in ChangeLog and Fill modes seems to set a line length
> somewhat less than 79. I generally follow what it tells me, but I can
> fix this.
> >
> >> + if (LABEL_REF_P (x))
> >> + output_asm_label (x);
> >> + else
> >> + output_addr_const (file, x);
> > Why does LABEL_REF need separate handling here?
>
> Mike, please respond?
The current code doesn't need special handling. I don't recall if earlier code
did, or I just assumed output_addr_const did not handle LABEL_REF's.
> > I don't much like penalising scalar single precision float like this.
> > But, this also hurts unaligned lwz... Do we have statistics on that?
> > Offline, I guess :-)
>
> Again, I'll defer to Mike on those details (online or offline). ;-)
I have rewritten this section. In particular rather than basing everything off
of the mode, I have a now have a more targeted approach that knows which
register, mode, and with sign extension requires D/DS/DQ addresses. Of course
this only works after register allocation. Before register allocation, we
still have to make a best guess based only on the mode.
--
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
prev parent reply other threads:[~2019-05-30 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 3:52 Bill Schmidt
2019-05-30 19:26 ` Segher Boessenkool
2019-05-30 19:48 ` Bill Schmidt
2019-05-30 20:38 ` Segher Boessenkool
2019-05-30 23:28 ` Michael Meissner [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=20190530215422.GA9844@ibm-toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.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).