Gabriel Dos Reis wrote:
> 
> If VRP is doing what you described in the comment as "its work", then
> VRP is broken.  Period.  The fix is to fix VRP.  It is such a C
> idomatic construct than I would not have expected any "optimizer" to
> break it.  And that is very worrisome and scary.
> 

Okay, VRP is not that broken in mainline, but only on a patch that I'm
working on.

By the way, how is this different than detecting a bound on:

{
  int foo[1335];

  for (i = 0; i < some_param; i++)
    foo[i];
}

vs.

{
  some_struct{ int foo[1335];} s;

  for (i = 0; i < some_param; i++)
    s.foo[i];
}

Reply via email to