From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH #2], PR target/81959, Fix ++int to _Float128 conversion on power9
Date: Fri, 01 Dec 2017 23:46:00 -0000 [thread overview]
Message-ID: <20171201234609.GA4042@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <20171201233339.GI10515@gate.crashing.org>
On Fri, Dec 01, 2017 at 05:33:39PM -0600, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Nov 30, 2017 at 04:52:44PM -0500, Michael Meissner wrote:
> > No, then it tends to generate worse code if it is done before the first split
> > pass (because it no longer keeps the address together). I've been thinking
> > that in general, we should replace these calls with a new predicate that before
> > register allocation allows normal memory addresses, but during/after RA, it
> > becomes more strict. In my experience, with RELOAD that wasn't feasible, but
> > LRA can handle it (and RELOAD is no longer an issue).
>
> Can't you use the "strict" arg to legitimate_address_p and friends?
Well legitimate_address_p allows various D-form address, pre-inc/pre-dec, etc.
It has no context on what the address is being used for. Secondary reload does
have the context, but I've seen post reload passes redo stuff (and typically
then it has to add more code to match the constraints once again).
> > > --- gcc/testsuite/gcc.target/powerpc/pr81959.c (revision 0)
> > > +++ gcc/testsuite/gcc.target/powerpc/pr81959.c (revision 0)
> > > @@ -0,0 +1,25 @@
> > > +/* { dg-do compile { target { powerpc64*-*-* && lp64 } } } */
> > > +/* { dg-require-effective-target powerpc_p9vector_ok } */
> > > +/* { dg-options "-mpower9-vector -O2 -mfloat128" } */
> >
> > powerpc*-*-*, or does that not work?
> >
> > It needs 64-bit because various machine independent parts of the compiler want
> > to use TImode if there is arithmetic support for KFmode to copy things, and
> > TImode isn't supported in 32-bit.
>
> That's what lp64 is for.
>
> > The __float128 support is not built if the compiler is a 32-bit compiler (the
> > enabler for _float128 is in linux64.h)
>
> So we need some bugzilla predicate for that really?
Or possibly implement the support in 32-bit compilers (and not break embedded
targets).
> Okay for trunk. Further improvements welcome ;-) Thanks!
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.vnet.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2017-12-01 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:51 Michael Meissner
2017-12-01 23:33 ` Segher Boessenkool
2017-12-01 23:46 ` Michael Meissner [this message]
2017-12-04 21:32 ` Michael Meissner
2017-12-11 16:10 ` 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=20171201234609.GA4042@ibm-tiger.the-meissners.org \
--to=meissner@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.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).