This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/80641] Warning with std::vector resize in loop
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 05 May 2017 15:04:05 +0000
- Subject: [Bug c++/80641] Warning with std::vector resize in loop
- Auto-submitted: auto-generated
- References: <bug-80641-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80641
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic,
| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-05-05
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=79095
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. The test case looks very similar to the one in bug 79095.
Improving the optimizer to prevent emitting these excessive memsets is the
ideal goal but in the instances when they do end up in the code, Jeff and I
discussed replacing them with traps instead (for memset under an option so
applications that rely on Physical Address Extension can continue to do so).