public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114252] Introducing bswapsi reduces code performance Date: Thu, 07 Mar 2024 10:47:43 +0000 [thread overview] Message-ID: <bug-114252-4-KlSJzJFIci@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114252-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114252 --- Comment #12 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- (In reply to Richard Biener from comment #10) > I think the target controls the "libcall" ABI that's used for calls to > libgcc, You have a pointer how to do it or an example? IIRC I looked into it quite a while ago, and it didn't allow to specify/adjust call_used_regs[] etc. > I think the target should implement an inline bswap, possibly via a > define_insn_and_split or define_split so the byte ops are only exposed > at a desired point; important points being lower_subreg (split-wide-types) > and register allocation - possibly lower_subreg should itself know > how to handle bswap (though the degenerate AVR case is quite special). That would result in SUBREGs all over the place. As Vladimir pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110093#c5 DFA doesn't handle subregs properly, and register alloc then uses extra reloads, bloating the code (not only in PR110093 but also 114243. Unlikely any pass will untangle the mess of four (set (subreg:QI (SI)) (subreg:QI (SI))) > Yeah. Or comparing to open-coding the bswap without going through the call. > I don't have a AVR libgcc around, but libgcc2.s has > > #ifdef L_bswapsi2 > SItype > __bswapsi2 (SItype u) > { > return ((((u) & 0xff000000u) >> 24) > | (((u) & 0x00ff0000u) >> 8) > | (((u) & 0x0000ff00u) << 8) > | (((u) & 0x000000ffu) << 24)); > } > #endif The libgcc side is not a problem at all, libgcc/config/avr/lib1funcs.S has: ;; swap two registers with different register number .macro bswap a, b eor \a, \b eor \b, \a eor \a, \b .endm #if defined (L_bswapsi2) ;; swap bytes ;; r25:r22 = bswap32 (r25:r22) DEFUN __bswapsi2 bswap r22, r25 bswap r23, r24 ret ENDF __bswapsi2 #endif /* defined (L_bswapsi2) */ #if defined (L_bswapdi2) ;; swap bytes ;; r25:r18 = bswap64 (r25:r18) DEFUN __bswapdi2 bswap r18, r25 bswap r19, r24 bswap r20, r23 bswap r21, r22 ret ENDF __bswapdi2 #endif /* defined (L_bswapdi2) */ There's currently no handcrafted bswap16 though.
next prev parent reply other threads:[~2024-03-07 10:47 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-06 10:01 [Bug tree-optimization/114252] New: " gjl at gcc dot gnu.org 2024-03-06 11:55 ` [Bug target/114252] " rguenth at gcc dot gnu.org 2024-03-06 11:59 ` rguenth at gcc dot gnu.org 2024-03-06 12:15 ` gjl at gcc dot gnu.org 2024-03-06 12:37 ` rguenth at gcc dot gnu.org 2024-03-06 16:12 ` gjl at gcc dot gnu.org 2024-03-06 17:18 ` rguenther at suse dot de 2024-03-07 7:45 ` rguenth at gcc dot gnu.org 2024-03-07 8:45 ` gjl at gcc dot gnu.org 2024-03-07 9:05 ` gjl at gcc dot gnu.org 2024-03-07 9:14 ` rguenth at gcc dot gnu.org 2024-03-07 9:42 ` rguenth at gcc dot gnu.org 2024-03-07 10:47 ` gjl at gcc dot gnu.org [this message] 2024-03-07 10:56 ` rguenth at gcc dot gnu.org 2024-03-07 14:12 ` gjl at gcc dot gnu.org 2024-03-07 15:02 ` pinskia at gcc dot gnu.org 2024-03-07 17:52 ` rguenther at suse dot de
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-114252-4-KlSJzJFIci@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: linkBe 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).