[LLVMbugs] [Bug 16557] New: -fno-exceptions behavior does not match GCC (or, -fcheck-new is not implemented)
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Sun Jul 7 12:01:48 PDT 2013
http://llvm.org/bugs/show_bug.cgi?id=16557
Bug ID: 16557
Summary: -fno-exceptions behavior does not match GCC (or,
-fcheck-new is not implemented)
Product: clang
Version: trunk
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangbugs at nondot.org
Reporter: eric at vangyzen.net
CC: dgregor at apple.com, llvmbugs at cs.uiuc.edu
Classification: Unclassified
Created attachment 10824
--> http://llvm.org/bugs/attachment.cgi?id=10824&action=edit
Test case
The attached test case, when compiled with "gcc -fno-exceptions -fcheck-new"
prints nothing and exits with a zero status. When compiled with llvm/clang 3.3
and ToT (with the same arguments), it segfaults in the member initializer.
Ideally, when using -fno-exceptions, clang would emit code to check the return
value of "new" before calling the constructor, regardless of that operator's
exception specification.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20130707/5ec2e122/attachment.html>
More information about the llvm-bugs
mailing list