public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/71218] Add a warning about "new T[integer-literal]"
[not found] <bug-71218-4@http.gcc.gnu.org/bugzilla/>
@ 2020-04-13 20:34 ` msebor at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: msebor at gcc dot gnu.org @ 2020-04-13 20:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71218
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Rather than warning for benign but inefficient code I'd find it more friendly
if GCC optimized it instead (if possible of course). In this case, it should
be possible to rewrite it as suggested (i.e., turn dynamic allocation into
automatic). A warning would then be useful if the automatic rewrite wasn't
possible for some reason.
Conversely, it could also turn stack allocation into dynamic for very large
sizes (under some option controlling the cut-off point). This would be
especially useful for VLAs.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-13 20:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-71218-4@http.gcc.gnu.org/bugzilla/>
2020-04-13 20:34 ` [Bug c++/71218] Add a warning about "new T[integer-literal]" msebor at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).