https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #7 from Andrew Pinski ---
This is also definitely a bug in MSVC and should reported to them.
ICC fixed their bug already even.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #6 from Andrew Pinski ---
icc version 2021.1.2 (gcc version 10.1.0 compatibility)
Has the same behavior as GCC.
While:
icc version 19.0.0.117 (gcc version 8.2.0 compatibility)
had the MSVC behavior
clang has the same behavior as GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #5 from jim.gray at atos dot net ---
I don't know if it makes any difference, but I ran with an older version of the
Intel C++ compiler on Linux, with the results below:
Good output when compiling with the Intel C++ compiler
on Cent
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #4 from Andrew Pinski ---
(In reply to jim.gray from comment #3)
> The "correct" answer is also provided by the Intel C++ compiler,
> so apparently GCC is the odd one out.
I think MSVC is the odd one out really. see below.
You can a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #3 from jim.gray at atos dot net ---
The "correct" answer is also provided by the Intel C++ compiler,
so apparently GCC is the odd one out.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109750
--- Comment #1 from Andrew Pinski ---
((UI64)source.sH.lower)
The question is source.sH.lower promoted to int rather than the underlying
type. Note clang has the same behavior as GCC here even. So I am thinking this
is a bug in MSVC rather tha
