[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Target Milestone|--- |4.9.2
 Status|NEW |RESOLVED

--- Comment #9 from Andrew Pinski  ---
Fixed for GCC 5 with r5-2621 and 4.9.2 with g:5456720833910e .

Basically The inlining of the ASAN_CHECK later on fixes the issue.

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[rguenth at gcc dot gnu.org]

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

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|4.9.4   |---

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

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

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|4.9.3   |4.9.4

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

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

--- Comment #8 from Jakub Jelinek  ---
GCC 4.9.3 has been released.

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

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

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|4.9.2   |4.9.3

--- Comment #7 from Jakub Jelinek  ---
GCC 4.9.2 has been released.

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

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

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|4.9.1   |4.9.2

--- Comment #6 from Jakub Jelinek  ---
GCC 4.9.1 has been released.

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|4.9.0   |4.9.1

--- Comment #5 from Jakub Jelinek  ---
GCC 4.9.0 has been released

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908

--- Comment #4 from Richard Biener  ---
PR39612?

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908

Jakub Jelinek  changed:

   What|Removed |Added

 CC||burnus at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek  ---
*** Bug 60649 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908

--- Comment #2 from Richard Biener  ---
There is a very old duplicate somewhere.  Happens with store-motion for a
simple

void foo (int n)
{
  int x, i;
  for (i = 0; i < n; ++i)
x = i;
  bar (&x);
}

IIRC.  Of course requires us to re-write x into SSA form later, so some more
"clever" testcase is required.  LIM does:

  :
  if (n_4(D) > 0)
goto ;
  else
goto ;

  :
  x_lsm.3_5 = x;

load of uninitialized x


  :
  # i_11 = PHI 
  x_lsm.3_1 = i_11;
  i_6 = i_11 + 1;
  if (n_4(D) > i_6)
goto ;
  else
goto ;

  :
  # x_lsm.3_9 = PHI 
  x = x_lsm.3_9;
  goto ;

now go find the duplicate ;)

[Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM

[mpolacek at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908

Marek Polacek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2014-01-22
 CC||mpolacek at gcc dot gnu.org
   Target Milestone|--- |4.9.0
 Ever confirmed|0   |1

--- Comment #1 from Marek Polacek  ---
Confirmed.