[Bug analyzer/105948] RFE: analyzer could check c++ placement-new sizes

2023-09-01 Thread vultkayn at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105948 --- Comment #3 from Benjamin Priour --- I believe the above patch resolves this PR. I'm letting it sip in trunk for a few days before marking it as solved.

[Bug analyzer/105948] RFE: analyzer could check c++ placement-new sizes

2023-09-01 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105948 --- Comment #2 from CVS Commits --- The trunk branch has been updated by Benjamin Priour : https://gcc.gnu.org/g:e7b267444045c507654a2a3f758efee5d5b550df commit r14-3632-ge7b267444045c507654a2a3f758efee5d5b550df Author: benjamin priour Date:

[Bug analyzer/105948] RFE: analyzer could check c++ placement-new sizes

2023-06-30 Thread vultkayn at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105948 --- Comment #1 from Benjamin Priour --- I'm writing a patch for this, and I've got support for non symbolic bounds. However, as I wrote my patch, a missing warning came up. Consider the test case: --- void var_too_short () { short s; long