This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A completely different approach to EH runtime
- To: hjl at valinux dot com
- Subject: Re: A completely different approach to EH runtime
- From: Mike Stump <mrs at windriver dot com>
- Date: Thu, 22 Feb 2001 14:47:51 -0800 (PST)
- Cc: gcc at gcc dot gnu dot org, geoffk at geoffk dot org, zackw at Stanford dot EDU
> Date: Thu, 22 Feb 2001 13:03:25 -0800
> From: "H . J . Lu" <hjl@valinux.com>
> To: Mike Stump <mrs@windriver.com>
> Cc: geoffk@geoffk.org, gcc@gcc.gnu.org, zackw@Stanford.EDU
> On Thu, Feb 22, 2001 at 12:57:44PM -0800, Mike Stump wrote:
> > Why is it impossible to run a mini testsuite to catch major problems
> > at install time, and only install, if the new one passes the
> > testsuite? Every program you worry about breaking could then have a
> > testcase in the testsuite, and install will only put it into lib
> > _after_ the testsuite runs with the new lib it is about to install.
> I am sure RedHat, SuSE, ... will do more than that for libgcc_s.so
> they provide. I am talking about a user builds/install a new gcc,
> which also comes with a libgcc_s.so.
As am I.