https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
Jonathan Wakely changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
--- Comment #8 from Jonathan Wakely ---
Yes, but it's only a missed-optimization bug so there are much higher
priorities.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
--- Comment #7 from AK ---
Is there a plan to push a patch for this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
--- Comment #6 from AK ---
> We can use memchr to find a char in a range of signed char, or even to find
> an int in a range of signed char, as long as we're careful about values.
+1, this approach should fix the bug i reported
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
AK changed:
What|Removed |Added
CC||hiraditya at msn dot com
--- Comment #5 from AK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
--- Comment #4 from Georg Sauthoff ---
Sam, thank you for the hint and surfacing it again.
(In reply to Jonathan Wakely from comment #2)
[..]
> I would prefer to do simply:
[..]
Yes, please go ahead with your approach.
> I think we're going
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
--- Comment #3 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #2)
> + using _ValT = typename iterator_traits<_InputIterator>::value_type;
> + if constexpr (is_same_v<_ValT, _Tp>)
> + if constexpr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
Jonathan Wakely changed:
What|Removed |Added
Keywords||missed-optimization
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
10 matches
Mail list logo
