From: Phil Edwards <phil@jaj.com>
To: law@redhat.com, bkoz@redhat.com
Cc: Janis Johnson <janis187@us.ibm.com>,
Jakub Jelinek <jakub@redhat.com>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
Mark Mitchell <mark@codesourcery.com>,
gcc@gcc.gnu.org,
"Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Subject: Re: GCC 3.2
Date: Mon, 19 Aug 2002 11:41:00 -0000 [thread overview]
Message-ID: <20020819144122.B23804@disaster.basement.lan> (raw)
In-Reply-To: <200208131649.g7DGnkK09005@porcupine.slc.redhat.com>
On Tue, Aug 13, 2002 at 10:49:46AM -0600, Jeff Law wrote:
> Right. That's one of the reasons why I mentioned in an earlier message
> that we need a test which verifies that all of the exported functions
> in libstdc++ (and libgcc) are maintained over time -- which has the
> side effect of being a reasonable tester for name mangling changes.
> We need ways to verify structure layouts aren't changing, etc etc.
In message < 20020812164321.A4428@us.ibm.com >, Janis Johnson writes:
> >and new compilers available when running the tests. I'm not at all sure
> >how to set up such tests for use with GCC. The test harness needs to
> >know about two compilers under test rather than one,
For some time now my nightly autocrasher[*] has built both the current trunk
and the current 3.whatever-the-previous-release-was branch. I've started
comparing exported symbol information from the libstdc++.so's from both
builds. (See the libstdc++ list archives of the last week or so; posts
from Benjamin and Ulrich and myself.)
I've verified that changing the size of an exported symbol triggers the
regression detection. Work yet to be done:
1) Test for layout changes, not just size changes.
2) Find a way of putting this into the v3 repository.
I've no ideas on (1). For (2) I'll be posting some thoughts on the v3
list later.
Phil
[*] "autobuilder" is just too positive and uplifing a name for something as
hacky as what I wrote.
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next prev parent reply other threads:[~2002-08-19 11:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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-02 4:58 ` PATCH to avoid copying tail padding (was: GCC 3.2) Jason Merrill
2002-08-12 8:47 ` GCC 3.2 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 [this message]
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
2002-07-27 22:19 Benjamin Kosnik
2002-07-28 9:40 ` Jakub Jelinek
[not found] <Pine.LNX.4.33.0208041756450.30248-100000@kern.srcf.societies.cam.ac.uk>
2002-08-04 10:24 ` Gerald Pfeifer
2002-08-12 19:05 Benjamin Kosnik
2002-10-18 17:23 gcc 3.2 Udo Tremel
2002-10-18 18:08 ` Mike Stump
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=20020819144122.B23804@disaster.basement.lan \
--to=phil@jaj.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=janis187@us.ibm.com \
--cc=kevin.hendricks@sympatico.ca \
--cc=law@redhat.com \
--cc=mark@codesourcery.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).