From: Alan Modra <amodra@gmail.com>
To: luoxhu <luoxhu@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
wschmidt@linux.ibm.com, gcc-patches@gcc.gnu.org,
linkw@gcc.gnu.org
Subject: Re: [PATCH] rs6000: Don't split constant oprator when add, move to temp register for future optimization
Date: Fri, 3 Apr 2020 22:43:49 +1030 [thread overview]
Message-ID: <20200403121349.GH4583@bubble.grove.modra.org> (raw)
In-Reply-To: <596ce54a-996c-3180-dbf1-df5e94ded4cb@linux.ibm.com>
On Fri, Apr 03, 2020 at 02:13:06PM +0800, luoxhu via Gcc-patches wrote:
> Seems PR94393? Yes, rs6000_emit_set_const calls rs6000_emit_set_long_const for DImode.
> I tried unsigned long like 0xabcd87654321, 0xffffabcd87654321 and 0xc000000000000000ULL,
> All of them are outside of loop even without my patch. No difference with or without
> Alan's patch.
Segher probably meant the part I'm working on and haven't posted yet,
fixing lots of problems with rs6000_rtx_costs. One of the improvements
I'm aiming for is that we should be able to emit code that loads
constants from memory without following optimisation passes converting
the loads from memory to those long sequences of dependent instructions.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-04-03 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 10:06 luoxhu
2020-03-26 15:18 ` will schmidt
2020-03-27 14:33 ` Segher Boessenkool
2020-03-30 3:59 ` luoxhu
2020-04-02 22:16 ` Segher Boessenkool
2020-04-03 6:13 ` luoxhu
2020-04-03 12:13 ` Alan Modra [this message]
2020-04-03 21:11 ` Segher Boessenkool
2020-04-03 23:51 ` Alan Modra
2020-04-07 21:47 ` Segher Boessenkool
2020-04-03 21:08 ` 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=20200403121349.GH4583@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@gcc.gnu.org \
--cc=luoxhu@linux.ibm.com \
--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).