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: [RFC Patch], PowerPC memory support pre-gcc9, patch #1
Date: Tue, 20 Mar 2018 20:35:00 -0000 [thread overview]
Message-ID: <20180320203247.GB12044@ibm-tiger.the-meissners.org> (raw)
In-Reply-To: <20180320130157.GG21977@gate.crashing.org>
On Tue, Mar 20, 2018 at 08:01:57AM -0500, Segher Boessenkool wrote:
> Hi! Some comments...
>
> On Wed, Mar 14, 2018 at 06:54:08PM -0400, Michael Meissner wrote:
> > The first patch in the series moves most of the reg_addr structure from
> > rs6000.c to rs6000-protos.h, so that in the next patch, we can start splitting
> > some of the address code to other files.
>
> Is that the correct header? It currently contains only function
> prototypes, and the name indicates that is what it should be.
>
> > 1) I was playing with making r12 be fixed with a new option (not in this
> > set of patches), and I noticed it wasn't reflected in the -mdebug=reg
> > debug dump, due to the debug dump being done before the conditional
> > registers are setup. I made the debug dump set conditional registers.
>
> Various ABIs use r12 for various things. It's also used for split stack.
> Besides that it is available for programs to do with as they please.
>
> > I likely will remove the undocumented toc-fusion all together, and eventually
> > rework the p8/p9 fusion support.
>
> Did it ever give any performance improvement?
>
> > 2018-03-14 Michael Meissner <meissner@linux.vnet.ibm.com>
> > * config/rs6000/rs6000-protos.h (regno_or_subregno): Add
> > declaration.
>
> There is a generic reg_or_subregno, how does this differ? If we need
> it please change the name so the difference is clear.
>
> It is very hard to review these patches. Please do patches that only
> move or rename things, not changing functionality, as separate patches
> (usually before everything else).
Ok, but if you want me to shove everything back into rs6000.c that simplifies
things. Some of the artiface is to support the reg_addr stuff in multiple
locations.
--
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
prev parent reply other threads:[~2018-03-20 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 23:01 Michael Meissner
2018-03-15 17:09 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #2 Michael Meissner
2018-03-20 13:32 ` Segher Boessenkool
2018-03-20 20:27 ` Michael Meissner
2018-03-15 23:33 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #3 Michael Meissner
2018-03-16 17:27 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #4 Michael Meissner
2018-03-20 16:21 ` Segher Boessenkool
2018-03-16 23:31 ` [RFC Patch], PowerPC memory support pre-gcc9, patch #1 Michael Meissner
2018-03-20 16:31 ` Segher Boessenkool
2018-03-20 13:04 ` Segher Boessenkool
2018-03-20 20:35 ` 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=20180320203247.GB12044@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).