public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/107099] New: uncprop a bit
@ 2022-09-30 14:41 amonakov at gcc dot gnu.org
  2022-10-06  8:53 ` [Bug tree-optimization/107099] uncprop a bit too eager rguenth at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: amonakov at gcc dot gnu.org @ 2022-09-30 14:41 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 107099
           Summary: uncprop a bit
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: amonakov at gcc dot gnu.org
  Target Milestone: ---

For the following testcase

#include <immintrin.h>

__attribute__((target("avx")))
int f(__m128i a[], long n)
{
    for (long i = 0; i < n; i++)
        if (!_mm_testz_si128(a[i], a[i]))
            return 0;
    return 1;
}

gcc -O2 generates

f:
        test    rsi, rsi
        jle     .L4
        xor     eax, eax
        jmp     .L3
.L10:
        add     rax, 1
        cmp     rsi, rax
        je      .L4
.L3:
        mov     rdx, rax
        sal     rdx, 4
        vmovdqa xmm0, XMMWORD PTR [rdi+rdx]
        xor     edx, edx
        vptest  xmm0, xmm0
        sete    dl
        je      .L10
        mov     eax, edx
        ret
.L4:
        mov     edx, 1
        mov     eax, edx
        ret

Note the redundant assignments to edx in the loop and compare with gcc -O2
-fdisable-tree-uncprop1

Also note that generally uncprop adds a data dependency where only a control
dependency existed, hurting speculative execution (hence more appropriate for
-Os than -O2).

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug tree-optimization/107099] uncprop a bit too eager
  2022-09-30 14:41 [Bug tree-optimization/107099] New: uncprop a bit amonakov at gcc dot gnu.org
@ 2022-10-06  8:53 ` rguenth at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-10-06  8:53 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-10-06
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |missed-optimization
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
uncprop should really be merged into the out-of-SSA coalescing machinery, it's
sole purpose is to avoid edge copies (which for constants you always have to
perform) when there's the possibility to generate reg-reg moves or coalescing
instead.

As such it's a heuristic that needs to be weighted against other heuristics
in place.

In this case we emit a copy instead of a zeroing (and zeroing is cheap on the
target, so zero might be a good candidate to special-case anyway), but we
have the zeroing in the loop body now.

The odd thing is that we perform desired coalescing:

Partition 0 (_1(D) - 1 6 11 )

(_1(D) is created for DECL_RESULT)

but expansion of __builtin_ia32_ptestz128 does

;; _11 = __builtin_ia32_ptestz128 (_4, _4);

(insn 17 16 18 (set (reg:SI 90)
        (const_int 0 [0])) "include/smmintrin.h":69:10 -1
     (nil))

(insn 18 17 19 (set (reg:CC 17 flags)
        (unspec:CC [
                (reg:V2DI 82 [ _4 ]) repeated x2
            ] UNSPEC_PTEST)) "include/smmintrin.h":69:10 -1
     (nil))

(insn 19 18 20 (set (strict_low_part (subreg:QI (reg:SI 90) 0))
        (eq:QI (reg:CC 17 flags)
            (const_int 0 [0]))) "include/smmintrin.h":69:10 -1
     (nil))

(insn 20 19 0 (set (reg:SI 86 [ <retval> ])
        (reg:SI 90)) "include/smmintrin.h":69:10 -1
     (nil))

which eventually ends up as

(insn 21 20 22 4 (set (reg:SI 86 [ <retval> ])
        (eq:SI (reg:CC 17 flags)
            (const_int 0 [0]))) "t.c":7:12 940 {*setcc_si_1_movzbl}
     (nil))
(jump_insn 22 21 23 4 (set (pc)
        (if_then_else (ne (reg:CC 17 flags)
                (const_int 0 [0]))
            (label_ref:DI 32)
            (pc))) "t.c":7:12 946 {*jcc}
     (int_list:REG_BR_PROB 59055804 (expr_list:REG_DEAD (reg:CCZ 17 flags)
            (nil)))

that's not forseen by coalescing - that _11 is actually not needed inside
the loop but only the CC result.

So heuristically we might want to disable uncprop when definitions from
calls (to [target] builtins) would be used.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-10-06  8:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-30 14:41 [Bug tree-optimization/107099] New: uncprop a bit amonakov at gcc dot gnu.org
2022-10-06  8:53 ` [Bug tree-optimization/107099] uncprop a bit too eager rguenth at gcc dot gnu.org

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).