https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
--- Comment #9 from Segher Boessenkool ---
(In reply to Martin Liška from comment #8)
> > We could make the "UInteger" type mean it is implemented with an "unsigned
> > int"
> > C type (or some other unsigned integer type).
>
> This would lead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
--- Comment #8 from Martin Liška ---
(In reply to Segher Boessenkool from comment #6)
> (In reply to Martin Liška from comment #5)
> > All right, so the meaning of the UInteger type is actually that users can't
> > set the flag/param to a negati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
--- Comment #7 from Segher Boessenkool ---
The documentation for UInteger also says
Positive values of the argument in
excess of @code{INT_MAX} wrap around zero.
so C "unsigned" types are natural for it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
--- Comment #6 from Segher Boessenkool ---
(In reply to Martin Liška from comment #5)
> All right, so the meaning of the UInteger type is actually that users can't
> set the flag/param to a negative value:
>
> $ gcc -fabi-version=-3 a.c
> gcc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
Martin Liška changed:
What|Removed |Added
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
Ever confi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
--- Comment #3 from Kewen Lin ---
(In reply to Andrew Pinski from comment #2)
> The other option handling bug report I saw dealing with the awk script was
> recorded as other.
Thanks Andrew! I just found there is a "other", how blind I am!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102440
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |other
--- Comment #2 from Andrew Pinski
