public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Bill Schmidt <wschmidt@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Fix some issues in rs6000_can_inline_p [PR102059]
Date: Fri, 3 Dec 2021 11:30:49 +0800	[thread overview]
Message-ID: <53d62777-589b-cc18-6363-41f78cb8db15@linux.ibm.com> (raw)
In-Reply-To: <Yalp+kT7xUqFWc5c@toto.the-meissners.org>

Hi Mike,

on 2021/12/3 上午8:51, Michael Meissner wrote:
> On Mon, Nov 29, 2021 at 10:57:12AM -0600, Segher Boessenkool wrote:
>> Why are there OPTION_MASKs for separate P10 fusion types here, as well as
>> MASK_P10_FUSION?
> 
> Well going back in time, before we used rs6000_isa_flags, we used the default
> flag word for MASK arguments.  Unfortunately, the default flag word is only
> 32-bits, and we needed more mask bits, so we moved to rs6000_isa_flags, which
> is HOST_WIDE_INT.
> 
> Unfortunately, the options infrastructure used 'OPTION_MASK_<foo>' instead of
> 'MASK_<foo>'.  So we have a bunch of macros in rs6000.h that map 'MASK_<foo>'
> to 'OPTION_MASK_<foo>'.
> 
> We should clean this up and use 'OPTION_MASK_<foo>' everywhere, but so far it
> hasn't percolated to the top as being important enough to do.
> 
> As new options are added, people just clone the code and add new macros, even
> though in theory nobody should be using MASK_P10_FUSION_<foo>.
> 

Thanks for the explanation on the history.  Fortunately now for Power10 fusion,
we have only one defined MASK_P10_FUSION but not the other MASK_P10_FUSION_<...>.

As you explained, I will use OPTION_MASK_P10_FUSION and OPTION_MASK_P8_FUSION
instead.

BR,
Kewen

  reply	other threads:[~2021-12-03  3:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  6:55 Kewen.Lin
2021-09-15  8:42 ` PING^1 " Kewen.Lin
2021-09-28  8:58   ` PING^2 " Kewen.Lin
2021-10-13  2:33     ` PING^3 " Kewen.Lin
2021-10-20  9:30       ` PING^4 " Kewen.Lin
2021-11-04 10:57         ` PING^5 " Kewen.Lin
2021-11-22  2:24           ` PING^6 " Kewen.Lin
2021-11-29 16:57 ` Segher Boessenkool
2021-12-03  0:51   ` Michael Meissner
2021-12-03  3:30     ` Kewen.Lin [this message]
2021-12-03  3:46   ` [PATCH v2] " Kewen.Lin
2021-12-03 23:23     ` Peter Bergner
2021-12-06  9:35       ` Martin Liška
2021-12-06 14:40         ` Peter Bergner
2021-12-06 13:06     ` Segher Boessenkool
2021-12-06 14:52       ` Peter Bergner
2021-12-07  3:42       ` Kewen.Lin

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=53d62777-589b-cc18-6363-41f78cb8db15@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@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).