https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #7 from Andrew Pinski ---
(In reply to Paul Caprioli from comment #6)
> This is the first patch I've submitted to GCC. I apologize for not knowing
> the proper tracking protocol. If there is anything more I can do, I welcome
> any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #6 from Paul Caprioli ---
One day, those older compilers will be considered ancient. Code written using
AVX512 intrinsics isn't the most portable anyway, and programmers are always
able to define their own macros (or just type a 0)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #5 from Andrew Pinski ---
Also bugzilla is not to track already submitted patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #4 from Andrew Pinski ---
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/657957.html
Adding a new macro for GCC 15 won't fix many many older compilers out there. So
most code will still use the old name for many many years to c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #3 from Paul Caprioli ---
Note that this is not for me; it's for everybody else.
The idea is for this to be the standard macro for specifying the IEEE rounding
to nearest attribute `roundTiesToEven`.
My contacts at Intel tell me the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
