https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
Jakub Miernik <jakub1miernik at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub1miernik at gmail dot com
--- Comment #22 from Jakub Miernik <jakub1miernik at gmail dot com> ---
(In reply to Uri Simchoni from comment #21)
> (In reply to Richard Biener from comment #18)
> > (In reply to Sven Hesse from comment #17)
> > > I still get this with gcc 12.2.0 (Gentoo 12.2.0 p9), but only when
> > > compiling
> > > with (at least with) -O1 -fsanitize=address, in addition to any warning
> > > flag
> > > that enables -Wmaybe-uninitialized (like -Wall, -Wextra or
> > > -Wuninitialized).
> > >
> > > -O0 and/or no ASan, and the offending code compiles cleanly without any
> > > warnings. Somehow, the combination of enabling ASan and optimization
> > > (anything > -O0, but not -Os) triggers it again, it seems?
> > >
> > > I can observe this with the testcase attached here in this bug report.
> >
> > -fsanitize=address is likely to derail optimization enough to make such
> > occurences more likely, I think we have plenty of duplicate bugreports
> > for this.
>
> So it seems this is still hapening with -O1 -fsanitize=address (occurring
> for me too with GCC 13.1.0), yet this specific bug is marked as "fixed" and
> there's a mention of duplicate bugreports (I can see one unconfirmed
> pointed-to by this issue). Is opening of another bug, focusing on -O1
> -fsanitize=address, going to help get this fixed?
I can confirm this is still valid.
Build with flags '-O1 -fsanitize=address -Wall -Werror' is still failing.
Tested for version 12.1, 12.2, 12.3, 13.1, 13.2
Shouldn't it be reopen?
If there is some other ticket related to it, could someone link it here?
