https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
--- Comment #7 from cerlane ---
(In reply to Jonathan Wakely from comment #5)
> You should have read https://gcc.gnu.org/bugs/ which explains what we need
> for a valid bug report, and would have done that before reporting it.
>
> You probably f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
cerlane changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
--- Comment #2 from cerlane ---
(In reply to Andrew Pinski from comment #1)
> Try 0x8000ULL
No unfortunately, it still returns 0x0.
Assignee: unassigned at gcc dot gnu.org
Reporter: cerlane at nscc dot sg
Target Milestone: ---
When returning the value 0x8000LL from a function (return type
int_fast64_t), the value becomes zero (0x0).
Is this a feature to guard against underflowing? If so, how can I
