public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrsam at courier-mta dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/13631] Problems in messages Date: Mon, 15 Jun 2009 11:13:00 -0000 [thread overview] Message-ID: <20090615111325.23926.qmail@sourceware.org> (raw) In-Reply-To: <bug-13631-4127@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from mrsam at courier-mta dot com 2009-06-15 11:13 ------- After staring at the code for a while, I'm leaning towards thinking that this change does not really change the application ABI, so the soname bump is not needed. As far as I can tell, there are no public members of std::messages, so applications never access instances of std::messages, the only thing they do is invoke the inlined methods, which call the virtual methods. I don't think that the addition of a class member affects the instances' vtable. Applications do not construct instances of std::messages. I don't think anything gets exposed that does that, this is done by libstdc++, so as long as libstdc++ gets rebuilt using the new class definition, that's all that's needed. use_facet() does not expose any code that constructs the class, that's done elsewhere. So, without any class members being accessed, and no constructions or destructions occuring as part of the ABI, scratch the soname bump -- I don't think it's needed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13631
next prev parent reply other threads:[~2009-06-15 11:13 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-13631-4127@http.gcc.gnu.org/bugzilla/> 2009-06-14 14:55 ` mrsam at courier-mta dot com 2009-06-14 17:14 ` mrsam at courier-mta dot com 2009-06-14 17:56 ` rguenth at gcc dot gnu dot org 2009-06-14 18:25 ` paolo dot carlini at oracle dot com 2009-06-14 18:57 ` mrsam at courier-mta dot com 2009-06-15 11:13 ` mrsam at courier-mta dot com [this message] 2009-06-15 11:36 ` paolo dot carlini at oracle dot com 2009-06-15 21:53 ` mrsam at courier-mta dot com 2009-06-15 22:06 ` paolo dot carlini at oracle dot com 2009-06-15 22:18 ` paolo dot carlini at oracle dot com 2009-06-15 23:10 ` peturrun at gmail dot com 2009-06-15 23:15 ` paolo dot carlini at oracle dot com 2009-06-16 3:51 ` mrsam at courier-mta dot com 2009-06-16 10:07 ` paolo dot carlini at oracle dot com 2009-06-16 11:08 ` mrsam at courier-mta dot com 2009-06-16 19:51 ` peturrun at gmail dot com 2009-06-16 21:54 ` mrsam at courier-mta dot com 2009-06-16 22:04 ` paolo dot carlini at oracle dot com 2009-06-19 0:47 ` mrsam at courier-mta dot com [not found] <bug-13631-4@http.gcc.gnu.org/bugzilla/> 2011-01-14 21:49 ` fdumont at gcc dot gnu.org 2011-05-05 21:34 ` paolo.carlini at oracle dot com 2011-05-05 22:27 ` mrsam@courier-mta.com 2014-12-03 19:47 ` fdumont at gcc dot gnu.org 2014-12-03 20:52 ` fdumont at gcc dot gnu.org 2015-03-18 16:18 ` redi at gcc dot gnu.org 2004-01-09 13:05 [Bug libstdc++/13631] New: " peturr02 at ru dot is 2004-01-09 13:07 ` [Bug libstdc++/13631] " peturr02 at ru dot is 2004-01-09 13:07 ` peturr02 at ru dot is 2004-01-11 10:52 ` paolo at gcc dot gnu dot org 2004-01-13 15:38 ` paolo at gcc dot gnu dot org 2004-01-13 16:19 ` paolo at gcc dot gnu dot org 2004-01-13 16:36 ` paolo at gcc dot gnu dot org 2004-01-14 16:47 ` peturr02 at ru dot is 2004-01-16 18:15 ` paolo at gcc dot gnu dot org 2004-01-19 11:44 ` peturr02 at ru dot is 2004-09-17 21:16 ` pcarlini at suse dot de
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=20090615111325.23926.qmail@sourceware.org \ --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).