https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:d9a0d692ffc6951c5670f54c3f4f17ec64a58600
commit r14-3486-gd9a0d692ffc6951c5670f54c3f4f17ec64a58600
Author: Andrew Pinski
Date: Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:6df8dcec7196e42ca2eed69e1ae455bae8d0fe93
commit r14-3485-g6df8dcec7196e42ca2eed69e1ae455bae8d0fe93
Author: Andrew Pinski
Date: Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-24
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
--- Comment #3 from Andrew Pinski ---
On the trunk we now get:
_25 = SR.116_117 == 0;
_27 = (unsigned char) _25;
_32 = _27 | SR.116_117;
Rather than:
_119 = MAX_EXPR <1, SR.115_117>;
But we should instead just get:
SR.116_117 | 1
Thou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
--- Comment #2 from Andrew Pinski ---
Hmm, I don't know if this related to the original issue but in .optimized we
have now:
# RANGE [irange] unsigned char [0, 1] NONZERO 0x1
# SR.115_117 = PHI <_119(9), SR.115_121(7)>
# RANGE [irange] uns
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
--- Comment #1 from Andrew Pinski ---
(In reply to Marc Glisse from comment #0)
> sum_vec gets relatively nice, short code. sum_array gets something uglier.
>
> _18 = &foo_5(D)->m_array;
> _6 = foo_5(D) + 24;
> if (_6 != _18)
That is rel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
