From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc@gcc.gnu.org
Cc: law@redhat.com
Subject: Re: GCC 3.2
Date: Mon, 12 Aug 2002 19:05:00 -0000 [thread overview]
Message-ID: <20020812190157.2508a7d6.bkoz@redhat.com> (raw)
> You could certainly do this too. The idea behind having it done in
> libstdc++ is that we can verify that sizes/layouts of any externally
> visible classes and structures don't change from one rev of libstdc++ to
> another. That in conjunction with testing the signatures of every
> externally visible function gives us a much better chance of keeping
> libstdc++ compatible from one rev to the next.
Right. I think this is the preferred way to go, it just requires much
(much much much) more work than simply swapping libstdc++.so's.
It looks like LSB is also interested in some kind of solution like this,
so perhaps there is some synergy there.
-benjamin
next reply other threads:[~2002-08-12 19:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 19:05 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 17:23 gcc 3.2 Udo Tremel
2002-10-18 18:08 ` Mike Stump
[not found] <Pine.LNX.4.33.0208041756450.30248-100000@kern.srcf.societies.cam.ac.uk>
2002-08-04 10:24 ` GCC 3.2 Gerald Pfeifer
2002-07-27 22:19 Benjamin Kosnik
2002-07-28 9:40 ` Jakub Jelinek
2002-07-27 1:01 Mark Mitchell
2002-07-27 1:28 ` Joe Buck
2002-07-27 1:30 ` Mark Mitchell
2002-07-27 3:30 ` Zack Weinberg
2002-07-29 4:26 ` Mark Mitchell
2002-07-29 5:00 ` Toon Moene
2002-07-27 16:26 ` Franz Sirl
2002-07-27 18:32 ` Jakub Jelinek
2002-07-30 6:49 ` Jason Merrill
2002-07-31 2:11 ` Jason Merrill
2002-07-31 5:05 ` Jason Merrill
2002-07-31 6:35 ` Neil Booth
2002-07-31 7:14 ` Neil Booth
2002-08-04 10:08 ` Joseph S. Myers
2002-07-31 10:45 ` Mark Mitchell
2002-08-01 14:42 ` Jason Merrill
2002-08-12 8:47 ` Jeff Law
2002-08-12 11:52 ` Jakub Jelinek
2002-08-12 13:14 ` Vladimir Makarov
2002-08-12 13:28 ` Jeff Law
2002-08-12 13:30 ` Jakub Jelinek
2002-08-12 16:42 ` Janis Johnson
2002-08-13 9:46 ` Jeff Law
2002-08-19 11:41 ` Phil Edwards
2002-08-20 21:38 ` Benjamin Kosnik
2002-08-21 4:31 ` Kevin B. Hendricks
2002-08-21 9:56 ` Benjamin Kosnik
2002-08-21 10:24 ` Kevin B. Hendricks
2002-08-21 11:24 ` Janis Johnson
2002-08-21 12:02 ` Phil Edwards
2002-08-21 14:53 ` Janis Johnson
2002-08-21 20:03 ` Benjamin Kosnik
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=20020812190157.2508a7d6.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
/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: link
Be 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).