This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/57997] Segmentation fault after returning valarray expression from an auto function
- From: "roystgnr at ices dot utexas.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 01 Aug 2013 17:12:39 +0000
- Subject: [Bug libstdc++/57997] Segmentation fault after returning valarray expression from an auto function
- Auto-submitted: auto-generated
- References: <bug-57997-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57997
--- Comment #6 from Roy Stogner <roystgnr at ices dot utexas.edu> ---
Copyright assignment shouldn't be a problem. The one serious non-technical
problem is going to be finding time to work on a patch.
The only technical issue I've discovered so far is that making this robust with
no efficiency penalty seems to be impossible without operator overloads that
take rvalue references. libstdc++ policy is that C++11 features are fine to
use if wrapped in
#if __cplusplus >= 201103L
and C++03 compatibility is maintained?