public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meisenmann.lba@fh-salzburg.ac.at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/60936] [4.9/5/6 Regression] Binary code bloat with std::string Date: Wed, 20 May 2015 08:44:00 -0000 [thread overview] Message-ID: <bug-60936-4-ya9zzWuV9y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60936-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60936 Markus Eisenmann <meisenmann.lba@fh-salzburg.ac.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meisenmann.lba@fh-salzburg. | |ac.at --- Comment #12 from Markus Eisenmann <meisenmann.lba@fh-salzburg.ac.at> --- Created attachment 35573 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35573&action=edit Using __throw_out_of_range (instead of __throw_out_of_range_fmt), if configured with --disable-libstdcxx-verbose My patch (file gcc-4.9-pr60936.patch) is a fix/work-around as suggested by Jonathan in Comment 4. Calling __throw_out_of_range_fmt is replaced by the (simpler) function __throw_out_of_range(), if the gcc-build is configured with the option --disable-libstdcxx-verbose. Note: I have used the previous call to __throw_out_of_range as used in GCC-release 4.8.4. Maybe the patch has to be applied with the option -p1 (or change the patch-file), because the path begins with 'gcc-4.9.2/' ... Following source-files will be changed (by this patch): [gcc-4.9.2/] libstdc++-v3/include/bits/basic_string.h [gcc-4.9.2/] libstdc++-v3/include/bits/functexcept.h [gcc-4.9.2/] libstdc++-v3/include/bits/stl_bvector.h [gcc-4.9.2/] libstdc++-v3/include/bits/stl_deque.h [gcc-4.9.2/] libstdc++-v3/include/bits/stl_vector.h [gcc-4.9.2/] libstdc++-v3/include/debug/array [gcc-4.9.2/] libstdc++-v3/include/experimental/string_view [gcc-4.9.2/] libstdc++-v3/include/ext/vstring.h [gcc-4.9.2/] libstdc++-v3/include/profile/array [gcc-4.9.2/] libstdc++-v3/include/std/array [gcc-4.9.2/] libstdc++-v3/include/std/bitset [gcc-4.9.2/] libstdc++-v3/src/c++11/functexcept.cc [gcc-4.9.2/] libstdc++-v3/testsuite/util/exception/safety.h Best regards, Markus
next prev parent reply other threads:[~2015-05-20 8:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-23 11:10 [Bug libstdc++/60936] New: " d.v.a at ngs dot ru 2014-04-23 12:12 ` [Bug libstdc++/60936] " d.v.a at ngs dot ru 2014-04-23 12:37 ` d.v.a at ngs dot ru 2014-07-17 10:00 ` [Bug libstdc++/60936] [4.9 Regression] " d.v.a at ngs dot ru 2014-07-19 9:57 ` redi at gcc dot gnu.org 2014-07-19 10:32 ` redi at gcc dot gnu.org 2014-11-19 13:27 ` rguenth at gcc dot gnu.org 2015-04-15 11:36 ` [Bug libstdc++/60936] [4.9/5 " d.v.a at ngs dot ru 2015-04-15 11:38 ` redi at gcc dot gnu.org 2015-04-15 11:40 ` redi at gcc dot gnu.org 2015-04-15 13:41 ` [Bug libstdc++/60936] [4.9/5/6 " d.v.a at ngs dot ru 2015-04-23 7:38 ` d.v.a at ngs dot ru 2015-05-20 8:44 ` meisenmann.lba@fh-salzburg.ac.at [this message] 2015-05-20 11:31 ` redi 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-60936-4-ya9zzWuV9y@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).