public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aivchenk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58525] New: __cxa_throw_bad_array_new_length is generated with -fno-exceptions
Date: Wed, 25 Sep 2013 07:22:00 -0000	[thread overview]
Message-ID: <bug-58525-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58525

            Bug ID: 58525
           Summary: __cxa_throw_bad_array_new_length is generated with
                    -fno-exceptions
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: aivchenk at gmail dot com

When I compile the following code (modified version of
g++.dg/cpp0x/bad_array_new1.C without try/catch):

// { dg-options -std=c++11 }
// { dg-do run }

#include <new>

void * f(int i)
{
  return new int[i];
}

int main()
{
      f(-1);
}

with -fno-exceptions option, I still get the call to
__cxa_throw_bad_array_new_length:

> nm ./bad_array_new1.o | grep cxa
    U __cxa_throw_bad_array_new_length


The same goes for __cxa_throw_bad_array_length


             reply	other threads:[~2013-09-25  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  7:22 aivchenk at gmail dot com [this message]
2013-09-25  7:26 ` [Bug c++/58525] " aivchenk at gmail dot com
2013-10-02 12:07 ` paolo.carlini at oracle dot com
2013-10-10 12:10 ` aivchenk at gmail dot com
2013-11-23 16:28 ` jason at gcc dot gnu.org
2013-12-30 22:13 ` reichelt at gcc dot gnu.org
2014-01-09  5:19 ` aivchenk at gmail dot com
2014-01-17 18:34 ` reichelt at gcc dot gnu.org
2024-03-27  1:28 ` pinskia at gcc dot gnu.org

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-58525-4@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: link
Be 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).