public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19351] [DR 624] operator new[] can return heap blocks which are too small Date: Mon, 20 Aug 2012 21:16:00 -0000 [thread overview] Message-ID: <bug-19351-4-yC0DuesQaN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19351-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351 --- Comment #27 from Florian Weimer <fw at gcc dot gnu.org> 2012-08-20 21:13:29 UTC --- Author: fw Date: Mon Aug 20 21:13:23 2012 New Revision: 190546 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190546 Log: Fix PR C++/19351: integer overflow in operator new[] 2012-08-20 Florian Weimer <fweimer@redhat.com> PR c++/19351 * call.c (build_operator_new_call): Add size_check argument and evaluate it. * cp-tree.h (build_operator_new_call): Adjust declaration. * init.c (build_new_1): Compute array size check and apply it. 2012-08-10 Florian Weimer <fweimer@redhat.com> PR c++/19351 * g++.dg/init/new38.C: New test. * g++.dg/init/new39.C: New test. Added: trunk/gcc/testsuite/g++.dg/init/new38.C trunk/gcc/testsuite/g++.dg/init/new39.C Modified: trunk/gcc/ChangeLog trunk/gcc/cp/call.c trunk/gcc/cp/cp-tree.h trunk/gcc/cp/init.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-08-20 21:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19351-4@http.gcc.gnu.org/bugzilla/> 2011-01-22 21:27 ` [Bug c++/19351] " fw at gcc dot gnu.org 2011-05-24 13:00 ` redi at gcc dot gnu.org 2011-05-24 20:12 ` fw at gcc dot gnu.org 2012-02-07 21:34 ` [Bug c++/19351] [DR 624] " redi at gcc dot gnu.org 2012-07-17 9:08 ` fweimer at redhat dot com 2012-08-20 21:16 ` fw at gcc dot gnu.org [this message] 2012-08-20 21:26 ` fw at gcc dot gnu.org 2012-10-01 8:12 ` jakub at gcc dot gnu.org 2014-02-16 10:01 ` jackie.rosen at hushmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-19351-4-yC0DuesQaN@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).