Re: [PATCH] toplev: use HOST_WIDE_INT for local_tick to prevent overflow

Hi Richard, The gcc devs have apparently declined to do anything about this bug (it's marked as "RESOLVED WONTFIX") and don't care much about plugins I guess: , so I won't be sending a v2. However, On Thu, Apr 7, 2022 at 8:30 AM Richard Biener

Re: [PATCH] toplev: use HOST_WIDE_INT for local_tick to prevent overflow

On Thu, Apr 7, 2022 at 12:44 AM Jason A. Donenfeld via Gcc-patches wrote: > > In gcc/toplev.c, there's the comment: > > /* A local time stamp derived from the time of compilation. It will be > zero if the system cannot provide a time. It will be -1u, if the > user has specified a part

Re: [PATCH] toplev: use HOST_WIDE_INT for local_tick to prevent overflow

On Wed, Apr 6, 2022 at 3:44 PM Jason A. Donenfeld wrote: > > In gcc/toplev.c, there's the comment: > > /* A local time stamp derived from the time of compilation. It will be > zero if the system cannot provide a time. It will be -1u, if the > user has specified a particular random see

[PATCH] toplev: use HOST_WIDE_INT for local_tick to prevent overflow

In gcc/toplev.c, there's the comment: /* A local time stamp derived from the time of compilation. It will be zero if the system cannot provide a time. It will be -1u, if the user has specified a particular random seed. */ unsigned local_tick; This is affirmed by init_local_tick()'