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 2/2] xtensa: Reflect the 32-bit Integer Divide Option
Date: Fri, 13 May 2022 02:37:18 -0700	[thread overview]
Message-ID: <CAMo8Bf+KccQmoG_jAjX8wyLKfjFTVUrmBj1mpBdC4Q0pAm4ugg@mail.gmail.com> (raw)
In-Reply-To: <5f99c6da-aa0c-5384-ee48-3556a03a6bf0@yahoo.co.jp>

On Fri, May 6, 2022 at 3:36 AM Takayuki 'January June' Suwa via
Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> On Espressif's ESP8266 (based on Tensilica LX106, no hardware divider),
> this patch reduces the size of each:
>
>    __moddi3() @ libgcc.a :  969 -> 301 (saves 668)
>    __divmoddi4()         : 1111 -> 426 (saves 685)
>    __udivmoddi4()        : 1043 -> 319 (saves 724)
>
> in bytes, respectively.
>
> gcc/ChangeLog:
>
>         * config/xtensa/xtensa.h (TARGET_HAS_NO_HW_DIVIDE): New macro
>         definition.
> ---
>   gcc/config/xtensa/xtensa.h | 5 +++++
>   1 file changed, 5 insertions(+)

Regtested for target=xtensa-linux-uclibc, there's new regression in
gcc.c-torture/execute/20101011-1.c
related to division by 0 implemented as an invalid opcode exception
that the kernel should convert to division by 0 signal, but does not.
It should be fixed in the kernel.

Committed to master.

-- 
Thanks.
-- Max

      reply	other threads:[~2022-05-13  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 10:34 Takayuki 'January June' Suwa
2022-05-13  9:37 ` 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+KccQmoG_jAjX8wyLKfjFTVUrmBj1mpBdC4Q0pAm4ugg@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).