public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "klepikov.alex+bugs at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49263] SH Target: underutilized "TST #imm, R0" instruction Date: Wed, 24 May 2023 11:40:45 +0000 [thread overview] Message-ID: <bug-49263-4-WVGtNZy3dl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49263-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49263 --- Comment #35 from Alexander Klepikov <klepikov.alex+bugs at gmail dot com> --- (In reply to Oleg Endo from comment #34) > Bit-tests of char and unsigned char should be covered by the test-suite and > should work -- at least originally. However, what might be triggering this > problem is the '== FLAG' comparison. When I was working on this issue I > only used '== 0' or '!= 0' comparison. I can imagine that your test code > triggers some other middle end optimizations and hence we get this. Yes, I am sure that the problem is the '== FLAG' comparison. Before I reported that bug, I tried to bypass it and this macro does not produce shift instructions even on GCC 4.7: #define BIT_MASK_IS_SET_(VALUE, BITMASK)\ ({int _value = VALUE & BITMASK,\ _result;\ if (_value == BITMASK){\ _result = 1;\ }\ else {\ _result = 0;\ }\ _result;}) So this is definitely the comparison. > > Can you try to rewrite your test code to something like this? > > unsigned int f(char v){ > return (v & FLAG) != 0; > } > > ... and see if it generates the tst instruction as expected? > As I understand, you meant the following (I added new functions at the end of file): $ cat f.c #define ADDR 0xFFFF0000 #define P ((unsigned char *)ADDR) #define FLAG 0x40 #define S 7 unsigned char f_char_var(char v){ return (v & FLAG) == FLAG; } unsigned char f_unsigned_char_var(unsigned char v){ return (v & FLAG) == FLAG; } unsigned char f_symbol(void){ return (*P & FLAG) == FLAG; } unsigned char f_symbol_zero(void){ return (*P & FLAG) == 0; } unsigned char f_symbol_non_zero(void){ return (*P & FLAG) != 0; } Compiler flags: -c -mrenesas -m2e -mb -O -fno-toplevel-reorder With patch disabled: $ cat f_clean.s .file "f.c" .text .text .align 1 .global _f_char_var .type _f_char_var, @function _f_char_var: sts.l pr,@-r15 mov.l .L3,r1 jsr @r1 exts.b r4,r4 mov r4,r0 and #1,r0 lds.l @r15+,pr rts nop .L4: .align 2 .L3: .long ___ashiftrt_r4_6 .size _f_char_var, .-_f_char_var .align 1 .global _f_unsigned_char_var .type _f_unsigned_char_var, @function _f_unsigned_char_var: sts.l pr,@-r15 mov.l .L7,r1 jsr @r1 exts.b r4,r4 mov r4,r0 and #1,r0 lds.l @r15+,pr rts nop .L8: .align 2 .L7: .long ___ashiftrt_r4_6 .size _f_unsigned_char_var, .-_f_unsigned_char_var .align 1 .global _f_symbol .type _f_symbol, @function _f_symbol: sts.l pr,@-r15 mov.l .L11,r1 mov.b @r1,r4 mov.l .L12,r1 jsr @r1 nop mov r4,r0 and #1,r0 lds.l @r15+,pr rts nop .L13: .align 2 .L11: .long -65536 .L12: .long ___ashiftrt_r4_6 .size _f_symbol, .-_f_symbol .align 1 .global _f_symbol_zero .type _f_symbol_zero, @function _f_symbol_zero: mov.l .L15,r1 mov.b @r1,r0 tst #64,r0 rts movt r0 .L16: .align 2 .L15: .long -65536 .size _f_symbol_zero, .-_f_symbol_zero .align 1 .global _f_symbol_non_zero .type _f_symbol_non_zero, @function _f_symbol_non_zero: sts.l pr,@-r15 mov.l .L19,r1 mov.b @r1,r4 mov.l .L20,r1 jsr @r1 nop mov r4,r0 and #1,r0 lds.l @r15+,pr rts nop .L21: .align 2 .L19: .long -65536 .L20: .long ___ashiftrt_r4_6 .size _f_symbol_non_zero, .-_f_symbol_non_zero .ident "GCC: (GNU) 12.3.0" With patch enabled: $ cat f.s .file "f.c" .text .text .align 1 .global _f_char_var .type _f_char_var, @function _f_char_var: mov r4,r0 tst #64,r0 mov #-1,r0 rts negc r0,r0 .size _f_char_var, .-_f_char_var .align 1 .global _f_unsigned_char_var .type _f_unsigned_char_var, @function _f_unsigned_char_var: mov r4,r0 tst #64,r0 mov #-1,r0 rts negc r0,r0 .size _f_unsigned_char_var, .-_f_unsigned_char_var .align 1 .global _f_symbol .type _f_symbol, @function _f_symbol: mov.l .L4,r1 mov.b @r1,r0 tst #64,r0 mov #-1,r0 rts negc r0,r0 .L5: .align 2 .L4: .long -65536 .size _f_symbol, .-_f_symbol .align 1 .global _f_symbol_zero .type _f_symbol_zero, @function _f_symbol_zero: mov.l .L7,r1 mov.b @r1,r0 tst #64,r0 rts movt r0 .L8: .align 2 .L7: .long -65536 .size _f_symbol_zero, .-_f_symbol_zero .align 1 .global _f_symbol_non_zero .type _f_symbol_non_zero, @function _f_symbol_non_zero: mov.l .L10,r1 mov.b @r1,r0 tst #64,r0 mov #-1,r0 rts negc r0,r0 .L11: .align 2 .L10: .long -65536 .size _f_symbol_non_zero, .-_f_symbol_non_zero .ident "GCC: (GNU) 12.3.0" > I'm not sure what the purpose of the '-mdisable-dynshift' option would be > here though. For '-m2e' TARGET_DYNSHIFT is already 'false'. So the option > seems misnamed. I choose that name because I wanted to disable dynamic shift instructions for all CPUs. I did not hope that it will affect SH-2E code in such way. I can rewrite the patch so that it only affects CPUs that do not support dynamic shifts and disables library call for dynamic shifts. I'll do it anyway because I need it badly. How do you think, what name of option would be better: '-mdisable-dynshift-libcall' or '-mhw-shift'? Or if you want, please suggest another one. Thank you!
next prev parent reply other threads:[~2023-05-24 11:40 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-01 20:17 [Bug target/49263] New: " oleg.endo@t-online.de 2011-06-01 20:42 ` [Bug target/49263] " oleg.endo@t-online.de 2011-06-12 23:12 ` kkojima at gcc dot gnu.org 2011-06-19 16:42 ` oleg.endo@t-online.de 2011-06-22 22:34 ` kkojima at gcc dot gnu.org 2011-06-26 22:31 ` oleg.endo@t-online.de 2011-06-27 5:15 ` kkojima at gcc dot gnu.org 2011-10-09 23:35 ` oleg.endo@t-online.de 2011-10-10 1:32 ` kkojima at gcc dot gnu.org 2011-10-10 23:48 ` oleg.endo@t-online.de 2011-10-11 1:47 ` kkojima at gcc dot gnu.org 2011-10-13 22:55 ` oleg.endo@t-online.de 2011-10-14 23:06 ` kkojima at gcc dot gnu.org 2011-10-15 2:33 ` kkojima at gcc dot gnu.org 2011-11-20 14:20 ` oleg.endo@t-online.de 2011-12-29 1:09 ` oleg.endo@t-online.de 2012-02-26 16:28 ` olegendo at gcc dot gnu.org 2012-02-26 23:29 ` olegendo at gcc dot gnu.org 2012-08-27 19:52 ` olegendo at gcc dot gnu.org 2012-10-28 22:02 ` olegendo at gcc dot gnu.org 2012-10-31 13:47 ` olegendo at gcc dot gnu.org 2013-12-08 13:47 ` olegendo at gcc dot gnu.org 2013-12-17 12:37 ` olegendo at gcc dot gnu.org 2014-12-30 18:45 ` olegendo at gcc dot gnu.org 2015-01-24 13:05 ` olegendo at gcc dot gnu.org 2015-01-26 23:57 ` olegendo at gcc dot gnu.org 2023-05-12 11:46 ` klepikov.alex+bugs at gmail dot com 2023-05-23 12:34 ` klepikov.alex+bugs at gmail dot com 2023-05-23 12:35 ` klepikov.alex+bugs at gmail dot com 2023-05-23 19:05 ` olegendo at gcc dot gnu.org 2023-05-24 11:40 ` klepikov.alex+bugs at gmail dot com [this message] 2023-05-24 11:57 ` olegendo at gcc dot gnu.org 2023-05-24 13:34 ` klepikov.alex+bugs at gmail dot com 2023-05-24 15:00 ` olegendo at gcc dot gnu.org 2023-05-25 17:53 ` klepikov.alex+bugs at gmail dot com 2023-05-25 21:32 ` olegendo at gcc dot gnu.org 2023-05-26 12:03 ` klepikov.alex+bugs at gmail dot com 2023-05-26 17:44 ` olegendo at gcc dot gnu.org 2023-05-28 10:24 ` klepikov.alex+bugs at gmail dot com 2023-05-28 10:48 ` olegendo at gcc dot gnu.org 2023-05-29 14:54 ` klepikov.alex+bugs at gmail dot com 2023-05-30 1:48 ` egallager at gcc dot gnu.org 2023-05-30 1:56 ` olegendo at gcc dot gnu.org 2023-05-30 12:42 ` klepikov.alex+bugs at gmail dot com 2023-05-30 19:57 ` olegendo at gcc dot gnu.org 2023-05-30 20:00 ` 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-49263-4-WVGtNZy3dl@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).