https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127772

Drea Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2026-10-11
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
           Keywords|                            |ice-checking

--- Comment #1 from Drea Pinski <pinskia at gcc dot gnu.org> ---
```
#define SREAL_MAX_EXP (INT_MAX / 4)
...
    gcc_checking_assert (s <= SREAL_MAX_EXP);
    gcc_checking_assert (s >= -SREAL_MAX_EXP);

    /* Overflows/drop to 0 could be handled gracefully, but hopefully we do not
       need to do so.  */
    gcc_checking_assert (m_exp + s <= SREAL_MAX_EXP);
    gcc_checking_assert (m_exp + s >= -SREAL_MAX_EXP);
```


```
           int shift = opt_for_fn (node->decl,
                                   param_ipa_cp_profile_runtime_scaling);
           overall_scaled_runtime += frt.shift(-shift);
```
```
-param=ipa-cp-profile-runtime-scaling=
Common Joined UInteger Var(param_ipa_cp_profile_runtime_scaling) Init(19) Param
Optimization
With profile feedback, by how many bits to shift the run-time before it is used
as the basis for IPA-CP evaluations.

```

I wonder if we should just limit this param to say 1000 and not worry about it.

Reply via email to