public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109874] [SH] GCC 13's -Os code is 50% bigger than GCC 4's
Date: Tue, 16 May 2023 12:16:47 +0000	[thread overview]
Message-ID: <bug-109874-4-nmu1jRknjP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109874-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109874

--- Comment #1 from Marc Poulhiès <dkm at gcc dot gnu.org> ---
Forcing GCC 13 to emit non-PIC (as gcc4) code shaves a few insns, down to 28.

```
_SetupCartCHRMapping:
        mov     r4,r1
        mov.l   .L3,r2
        shlr8   r1
        shlr2   r1
        add     #-1,r1
        mov.l   r1,@r2
        mov     r4,r1
        shlr8   r1
        mov.l   .L4,r2
        shlr    r1
        shlr2   r1
        add     #-1,r1
        mov.l   r1,@r2
        mov     r4,r1
        shlr8   r1
        mov.l   .L5,r2
        shlr2   r1
        shlr2   r1
        shlr8   r4
        add     #-1,r1
        shlr2   r4
        mov.l   r1,@r2
        shlr    r4
        mov.l   .L6,r1
        shlr2   r4
        add     #-1,r4
        rts     
        mov.l   r4,@r1
.L3:
        .long   _CHRmask1
.L4:
        .long   _CHRmask2
.L5:
        .long   _CHRmask4
.L6:
        .long   _CHRmask8
_CHRmask8:
        .zero   4
_CHRmask4:
        .zero   4
_CHRmask2:
        .zero   4
_CHRmask1:
        .zero   4
```

  reply	other threads:[~2023-05-16 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 10:51 [Bug target/109874] New: " paul at crapouillou dot net
2023-05-16 12:16 ` dkm at gcc dot gnu.org [this message]
2023-05-17  7:06 ` [Bug target/109874] " rguenth at gcc dot gnu.org
2023-07-07  6:12 ` olegendo at gcc dot gnu.org

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=bug-109874-4-nmu1jRknjP@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).