public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	Arvind Sankar <nivedita@alum.mit.edu>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Use predicates for RTL objects
Date: Thu, 08 Aug 2019 16:48:00 -0000	[thread overview]
Message-ID: <1aed8fb5-a5f0-c658-9db4-cb92ac75de16@redhat.com> (raw)
In-Reply-To: <20190805182926.GK31406@gate.crashing.org>

On 8/5/19 12:29 PM, Segher Boessenkool wrote:
> On Mon, Aug 05, 2019 at 02:14:50PM -0400, Arvind Sankar wrote:
>> On Mon, Aug 05, 2019 at 12:48:46PM -0500, Segher Boessenkool wrote:
>>> First: do you have a copyright assignment?  See
>>>   https://gcc.gnu.org/contribute.html
>>> for instructions.
>>
>> Nope, is this really substantial enough to warrant one?
> 
> Some might say it is, the sheer amount of code changed :-)  If some
> maintainer okays it without assignment, that is fine with me of course.
> 
> This is also easier if it is all machine-generated and nice simple
> patches :-)
If it's entirely machine generated and you don't want to do a copyright
assignment, then the way to go will be for someone with an assignment to
run the scripts and commit the change.  Then we'd only need an
assignment if we wanted the scripts in the repo.



> 
>>>> -/* Predicate yielding true iff X is an rtx for a double-int.  */
>>>> +/* Predicate yielding true iff X is an rtx for a floating point constant.  */
>>>>  #define CONST_DOUBLE_AS_FLOAT_P(X) \
>>>>    (GET_CODE (X) == CONST_DOUBLE && GET_MODE (X) != VOIDmode)
>>>
>>> Is const_double really only used for floating point these days?
> 
>> Are you asking if the CONST_DOUBLE_AS_INT_P possibility is dead code
>> now? That's beyond my current level of understanding of the code,
>> hopefully someone else will chime in.
> 
> I am asking if the change to this comment is correct.
I thought we used CONST_DOUBLE for scalar constants that are wider than
a HOST_WIDE_INT, or perhaps wider than 2 HOST_WIDE_INTs.  If that's
still the case, then the comment change is wrong.

Jeff

  parent reply	other threads:[~2019-08-08 16:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 17:38 Arvind Sankar
2019-08-02 17:50 ` Segher Boessenkool
2019-08-02 17:55   ` Arvind Sankar
2019-08-02 18:53     ` Segher Boessenkool
2019-08-02 19:22       ` Arvind Sankar
2019-08-05 17:18         ` Arvind Sankar
     [not found]         ` <20190805170908.GA1044536@rani.riverdale.lan>
2019-08-05 17:49           ` Segher Boessenkool
2019-08-05 18:14             ` Arvind Sankar
2019-08-05 18:29               ` Segher Boessenkool
2019-08-05 18:34                 ` Arvind Sankar
2019-08-08 16:48                 ` Jeff Law [this message]
2019-08-08 17:01                   ` Jakub Jelinek
2019-08-08 17:53                   ` Segher Boessenkool
2019-08-08 19:26                   ` Arvind Sankar
2019-08-06  3:11               ` Arvind Sankar
2019-08-06  3:11                 ` [PATCH v2 03/18] Use CONST_INT_P macro Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 02/18] Use CONST_INT_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_INT Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 04/18] Use CONST_WIDE_INT_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_WIDE_INT_P Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 05/18] Use CONST_FIXED_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_FIXED Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 10/18] Use CONST_STRING_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_STRING Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 08/18] Use CONST_VECTOR_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_VECTOR Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 07/18] Add CONST_VECTOR_P rtx_code predicate Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 13/18] Use MEM_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh MEM Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 12/18] Use SUBREG_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh SUBREG Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 14/18] Use LABEL_REF_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh LABEL_REF Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 06/18] Use CONST_DOUBLE_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh CONST_DOUBLE Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 15/18] Use LABEL_REF_P macro Arvind Sankar
2019-08-06  3:12                 ` [PATCH v2 01/18] Fix CONST_DOUBLE_AS_FLOAT_P comment Arvind Sankar
2019-08-06  3:13                 ` [PATCH v2 11/18] Use REG_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh REG Arvind Sankar
2019-08-06  3:13                 ` [PATCH v2 16/18] Use SYMBOL_REF_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh SYMBOL_REF Arvind Sankar
2019-08-06  3:13                 ` [PATCH v2 18/18] Use DEBUG_INSN_P macro. Autogenerated patch by running ../contrib/rtl-pred.sh DEBUG_INSN_P Arvind Sankar
2019-08-06  3:19                 ` [PATCH v2 09/18] Add CONST_STRING_P rtx_code predicate Arvind Sankar
2019-08-06  6:56                 ` [PATCH v2 17/18] Use SYMBOL_REF_P macro Arvind Sankar

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=1aed8fb5-a5f0-c658-9db4-cb92ac75de16@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nivedita@alum.mit.edu \
    --cc=segher@kernel.crashing.org \
    /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).