public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Sandiford <richard.sandiford@arm.com>,
	 Uros Bizjak <ubizjak@gmail.com>,
	Bernd Edlinger <bernd.edlinger@hotmail.de>
Subject: Re: [PATCH v4 04/12] Remove MAX_BITSIZE_MODE_ANY_INT
Date: Tue, 25 May 2021 16:37:16 +0200	[thread overview]
Message-ID: <CAFiYyc1pdzPEd85sd-=dTKZipY0fMqJmv0Lb5S3SjWF20fER3g@mail.gmail.com> (raw)
In-Reply-To: <20210518191646.3071005-5-hjl.tools@gmail.com>

On Tue, May 18, 2021 at 9:16 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> It is only defined for i386 and everyone uses the default:
>
>  #define MAX_BITSIZE_MODE_ANY_INT (64*BITS_PER_UNIT)
>
> Whatever problems we had before, they have been fixed now.

So I don't have a strong recollection here apart from memory usage
considerations with wide-int (possibly fixed by all the trailing-wide-int stuff
we now have).  So I'm fine if the target maintainer is - but then we probably
should remove all vestiges of non-default MAX_BITSIZE_MODE_ANY_INT,
or do we want to keep it just in case?

Thanks,
Richard.

>         * config/i386/i386-modes.def (MAX_BITSIZE_MODE_ANY_INT): Removed.
> ---
>  gcc/config/i386/i386-modes.def | 15 +++------------
>  1 file changed, 3 insertions(+), 12 deletions(-)
>
> diff --git a/gcc/config/i386/i386-modes.def b/gcc/config/i386/i386-modes.def
> index dbddfd8e48f..4e7014be034 100644
> --- a/gcc/config/i386/i386-modes.def
> +++ b/gcc/config/i386/i386-modes.def
> @@ -107,19 +107,10 @@ INT_MODE (XI, 64);
>  PARTIAL_INT_MODE (HI, 16, P2QI);
>  PARTIAL_INT_MODE (SI, 32, P2HI);
>
> -/* Mode used for signed overflow checking of TImode.  As
> -   MAX_BITSIZE_MODE_ANY_INT is only 160, wide-int.h reserves only that
> -   rounded up to multiple of HOST_BITS_PER_WIDE_INT bits in wide_int etc.,
> -   so OImode is too large.  For the overflow checking we actually need
> -   just 1 or 2 bits beyond TImode precision.  Use 160 bits to have
> -   a multiple of 32.  */
> +/* Mode used for signed overflow checking of TImode.  For the overflow
> +   checking we actually need just 1 or 2 bits beyond TImode precision.
> +   Use 160 bits to have a multiple of 32.  */
>  PARTIAL_INT_MODE (OI, 160, POI);
>
> -/* Keep the OI and XI modes from confusing the compiler into thinking
> -   that these modes could actually be used for computation.  They are
> -   only holders for vectors during data movement.  Include POImode precision
> -   though.  */
> -#define MAX_BITSIZE_MODE_ANY_INT (160)
> -
>  /* The symbol Pmode stands for one of the above machine modes (usually SImode).
>     The tm.h file specifies which one.  It is not a distinct mode.  */
> --
> 2.31.1
>

  reply	other threads:[~2021-05-25 14:37 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 19:16 [PATCH v4 00/12] Allow TImode/OImode/XImode in op_by_pieces operations H.J. Lu
2021-05-18 19:16 ` [PATCH v4 01/12] Add TARGET_READ_MEMSET_VALUE/TARGET_GEN_MEMSET_VALUE H.J. Lu
2021-05-19  9:25   ` Richard Biener
2021-05-19 12:55     ` H.J. Lu
2021-05-20 20:49       ` [PATCH] Add 3 target hooks for memset H.J. Lu
2021-05-21  5:42         ` Bernd Edlinger
2021-05-21 11:53           ` H.J. Lu
2021-05-25 14:34         ` Richard Biener
2021-05-25 15:11           ` H.J. Lu
2021-05-26  8:28             ` Richard Biener
2021-05-31 12:09               ` [PATCH] Add integer_extract and vec_const_duplicate optabs H.J. Lu
2021-05-31 12:46                 ` Richard Biener
2021-05-31 13:12                   ` H.J. Lu
2021-05-31 13:25                     ` Richard Biener
2021-05-31 13:32                       ` H.J. Lu
2021-05-31 13:36                         ` H.J. Lu
2021-05-31 20:22                         ` [PATCH v2] Add vec_const_duplicate optab and TARGET_GEN_MEMSET_SCRATCH_RTX H.J. Lu
2021-06-01  5:50                           ` Richard Sandiford
2021-06-01  5:54                             ` Jeff Law
2021-06-01 13:05                               ` H.J. Lu
2021-06-01 13:25                                 ` Richard Biener
2021-06-01 13:29                                   ` H.J. Lu
2021-06-01 14:21                                     ` Jeff Law
2021-06-01 23:07                                       ` H.J. Lu
2021-06-02  1:21                                         ` Hongtao Liu
2021-06-02  1:54                                           ` H.J. Lu
2021-06-02  7:02                                             ` Richard Biener
2021-06-02 13:50                                               ` H.J. Lu
2021-05-18 19:16 ` [PATCH v4 02/12] x86: Add TARGET_READ_MEMSET_VALUE/TARGET_GEN_MEMSET_VALUE H.J. Lu
2021-05-18 19:16 ` [PATCH v4 03/12] x86: Avoid stack realignment when copying data H.J. Lu
2021-05-18 19:16 ` [PATCH v4 04/12] Remove MAX_BITSIZE_MODE_ANY_INT H.J. Lu
2021-05-25 14:37   ` Richard Biener [this message]
2021-05-18 19:16 ` [PATCH v4 05/12] x86: Update piecewise move and store H.J. Lu
2021-05-18 19:16 ` [PATCH v4 06/12] x86: Add AVX2 tests for PR middle-end/90773 H.J. Lu
2021-05-18 19:16 ` [PATCH v4 07/12] x86: Add tests for piecewise move and store H.J. Lu
2021-05-18 19:16 ` [PATCH v4 08/12] x86: Also pass -mno-avx to pr72839.c H.J. Lu
2021-05-18 19:16 ` [PATCH v4 09/12] x86: Also pass -mno-avx to cold-attribute-1.c H.J. Lu
2021-05-18 19:16 ` [PATCH v4 10/12] x86: Also pass -mno-avx to sw-1.c for ia32 H.J. Lu
2021-05-18 19:16 ` [PATCH v4 11/12] x86: Update gcc.target/i386/incoming-11.c H.J. Lu
2021-05-18 19:16 ` [PATCH v4 12/12] constructor: Check if it is faster to load constant from memory H.J. Lu
2021-05-19  9:33   ` Richard Biener
2021-05-19 13:22     ` H.J. Lu
2021-05-19 13:27       ` Bernd Edlinger
2021-05-19 19:04         ` H.J. Lu
2021-05-20  6:57           ` Richard Biener
2021-05-20  7:51       ` Richard Biener
2021-05-20 14:03         ` [PATCH] constructor: Elide expand_constructor when can move by pieces is true H.J. Lu
2021-05-21  5:35           ` Bernd Edlinger
2021-05-21  6:57           ` Richard Biener
2021-05-21  7:30             ` Bernd Edlinger
2021-05-21 13:13               ` H.J. Lu
2021-05-21 13:09             ` [PATCH] Elide expand_constructor if move by pieces is preferred H.J. Lu

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='CAFiYyc1pdzPEd85sd-=dTKZipY0fMqJmv0Lb5S3SjWF20fER3g@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=richard.sandiford@arm.com \
    --cc=ubizjak@gmail.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).