You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Case 2 is another problem I stumbled upon trying to reproduce this on godbolt - which uses string_views (as in my original problem) - but on godbolt instead of getting unwanted unrolled code Clang was somehow unable to inline trivial std::ranges wrappers and for some reason thinks those same wrappers can throw exceptions? (though this might be an STL implementation issue).
Finally - trying to workaround this issue I could not use #pragma clang loop unroll( disable ) when using STL algorithms for the obvious reason being that pragma requiring to 'see' the loop directly following - can you add a pragma or an attribute or some other mechanism with which one could disable loop unrolling for a block of functions or a block of code or for an entire function (also affecting any inlined code).
The text was updated successfully, but these errors were encountered:
...unless, counterintuitively, combined with [[ flatten ]]
https://godbolt.org/z/s14W7W6Gf
This is demonstrated by case 1.
Case 2 is another problem I stumbled upon trying to reproduce this on godbolt - which uses string_views (as in my original problem) - but on godbolt instead of getting unwanted unrolled code Clang was somehow unable to inline trivial std::ranges wrappers and for some reason thinks those same wrappers can throw exceptions? (though this might be an STL implementation issue).
Finally - trying to workaround this issue I could not use #pragma clang loop unroll( disable ) when using STL algorithms for the obvious reason being that pragma requiring to 'see' the loop directly following - can you add a pragma or an attribute or some other mechanism with which one could disable loop unrolling for a block of functions or a block of code or for an entire function (also affecting any inlined code).
The text was updated successfully, but these errors were encountered: