[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 Andrew Macleod changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 --- Comment #8 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:0409aa5a2de9ce3164933814a4a7adc91f6acb96 commit r13-6850-g0409aa5a2de9ce3164933814a4a7adc91f6acb96 Author: Andrew MacLeod Date:

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 --- Comment #6 from Andrew Macleod --- Created attachment 54738 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54738=edit Patch to fix the issue Ah, sorry I missed that. OK, I traced it through. The problem turns out to be in the

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 --- Comment #5 from Richard Biener --- (In reply to Andrew Macleod from comment #4) > I think varying is the correct result tho? the branch is in BB28, but bb > 33 is a merge poi9nt again before bb 36, so we can't tell that it is > anything

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 --- Comment #4 from Andrew Macleod --- I think varying is the correct result tho? the branch is in BB28, but bb 33 is a merge poi9nt again before bb 36, so we can't tell that it is anything but varying? I see: [local count: 428124]: c_24

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 Richard Biener changed: What|Removed |Added CC||amacleod at redhat dot com ---

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 --- Comment #1 from Andrew Pinski --- c = realloc (p, -1); ... ; if (c != ((void *)0) ) support_exit_failure_impl (1, "tst-realloc.c", 120, "realloc (p, -1) succeeded."); c = p; ...

[Bug tree-optimization/109238] [13 Regression] tst-realloc.i:42:19: error: pointer ‘p’ may be used after ‘realloc’ [-Werror=use-after-free] in glibc tests

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109238 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|