[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Sebastian Huber
Subject: Re: [PATCH] GCC test case g++.dg/tls/thread_local5.C
Date: Fri, 12 Jul 2013 08:57:50 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130105 Thunderbird/17.0.2

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

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

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.

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]