[Bug middle-end/119600] HOST_WIDEST_FAST_INT should be used instead of long for BITMAP_WORD in bitmap.h

2025-05-21 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119600

Segher Boessenkool  changed:

   What|Removed |Added

 CC||segher at gcc dot gnu.org

--- Comment #3 from Segher Boessenkool  ---
(In reply to Andrew Pinski from comment #1)
> (In reply to Andrew Pinski from comment #0)
> > Looks like I missed this while I implemented PR 13987.
> 
> I missed it because I was changing HOST_WIDE_INT places and bitmap.h was
> changed to use long in r0-47360-g72e42e26cb760d which I assume to fix a
> similar compile time regression.

I did that because the bitmap stuff was very high in the overall profiles.  It
didn't have anything to do with a compile-time regression, at least not
directly.

[Bug middle-end/119600] HOST_WIDEST_FAST_INT should be used instead of long for BITMAP_WORD in bitmap.h

2025-04-03 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119600

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Last reconfirmed||2025-04-03

--- Comment #2 from Richard Biener  ---
Confirmed.

[Bug middle-end/119600] HOST_WIDEST_FAST_INT should be used instead of long for BITMAP_WORD in bitmap.h

2025-04-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119600

--- Comment #1 from Andrew Pinski  ---
(In reply to Andrew Pinski from comment #0)
> Looks like I missed this while I implemented PR 13987.

I missed it because I was changing HOST_WIDE_INT places and bitmap.h was
changed to use long in r0-47360-g72e42e26cb760d which I assume to fix a similar
compile time regression.