public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] xtensa: Turn on -fsplit-wide-types-early by default
Date: Mon, 15 Aug 2022 22:20:43 -0700	[thread overview]
Message-ID: <CAMo8Bf+cXmBZpVYhxsJrXsKeobBLJbjOgxEZTR0ZCHkm5F9txw@mail.gmail.com> (raw)
In-Reply-To: <f29ae60f-aa9c-2d60-1fd6-cb4089729331@yahoo.co.jp>

On Sun, Aug 14, 2022 at 2:31 AM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> Since GCC10, the "subreg2" optimization pass was no longer tied to enabling
> "subreg1" unless -fsplit-wide-types-early was turned on (PR88233).  However
> on the Xtensa port, the lack of "subreg2" can degrade the quality of the
> output code, especially for those that produce many D[FC]mode pseudos.
>
> This patch turns on -fsplit-wide-types-early by default in order to restore
> the previous behavior.
>
> gcc/ChangeLog:
>
>         * common/config/xtensa/xtensa-common.cc
>         (xtensa_option_optimization_table): Add OPT_fsplit_wide_types_early
>         for OPT_LEVELS_ALL in order to restore pre-GCC10 behavior.
> ---
>  gcc/common/config/xtensa/xtensa-common.cc | 2 ++
>  1 file changed, 2 insertions(+)

Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master.

-- 
Thanks.
-- Max

      reply	other threads:[~2022-08-16  5:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14  9:29 Takayuki 'January June' Suwa
2022-08-16  5:20 ` Max Filippov [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=CAMo8Bf+cXmBZpVYhxsJrXsKeobBLJbjOgxEZTR0ZCHkm5F9txw@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jjsuwa_sys3175@yahoo.co.jp \
    /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).