This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/60936] [4.9/5/6 Regression] Binary code bloat with std::string
- From: "d.v.a at ngs dot ru" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Apr 2015 13:40:58 +0000
- Subject: [Bug libstdc++/60936] [4.9/5/6 Regression] Binary code bloat with std::string
- Auto-submitted: auto-generated
- References: <bug-60936-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60936
--- Comment #9 from __vic <d.v.a at ngs dot ru> ---
For 4.9 this change was enough for me:
--- libstdc++-v3/src/c++11/functexcept.cc 2014-01-03 02:30:10.000000000
+0400
+++ libstdc++-v3/src/c++11/functexcept.cc 2014-11-06 18:40:20.000000000
+0300
@@ -89,6 +89,7 @@
void
__throw_out_of_range_fmt(const char* __fmt, ...)
{
+ __throw_out_of_range(__fmt);/*
const size_t __len = __builtin_strlen(__fmt);
// We expect at most 2 numbers, and 1 short string. The additional
// 512 bytes should provide more than enough space for expansion.
@@ -100,6 +101,7 @@
__gnu_cxx::__snprintf_lite(__s, __alloca_size, __fmt, __ap);
_GLIBCXX_THROW_OR_ABORT(out_of_range(_(__s)));
va_end(__ap); // Not reached.
+*/
}
void
But now it doesn't solve the problem.