Re: [PATCH] GCC test case g++.dg/tls/thread_local5.C

[Sebastian Huber]

On 2013-07-12 08:57, Sebastian Huber wrote:
> On 07/12/2013 02:48 AM, Ben Elliston wrote:
> > On Wed, Jul 10, 2013 at 11:58:36AM +0200, Sebastian Huber wrote:
> >
> > > How can I address this problem?  I don't think it is possible to
> > > alter the test in GCC to fix this problem.  One option is to store
> > > the latest exit code in testglue.c and print a new exit status it is
> > > different.
> >
> > A process can only have one exit code and so I think DejaGnu should
> > mimic this with its exit wrapper.  Isn't that what happens now?  I
> > don't think it is correct for "*** EXIT code" to be printed more than
> > once.
>
> Yes, a process has only one exit code, but you may have recursive calls to
> exit() or _exit() like in the GCC test case g++.dg/tls/thread_local5.C.

Since we have this recursive calls to exit() or _exit() in the GCC test suite 
DejaGNU should cope with it somehow.  We cannot predict the future so I think 
the only way is to print multiple "*** EXIT code" lines.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : address@hidden
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.