Lawrence Crowl writes:
> Inside a C++ .exp file, I want to know the compiler command that
> would be executed for a given dg-test command. That is, given
>
> set dg-do-what-default compile
> dg-test -keep-output $source "$options -I." ""
>
> what is a command that I can execute to compil
Inside a C++ .exp file, I want to know the compiler command that
would be executed for a given dg-test command. That is, given
set dg-do-what-default compile
dg-test -keep-output $source "$options -I." ""
what is a command that I can execute to compile the source file
without dejagnu try
On Mon, Aug 29, 2011 at 11:18 AM, Ken Werner wrote:
> On 08/25/2011 02:26 PM, Andrew Haley wrote:
>>
>> Throwing an exception through a segfault handler doesn't always work
>> on ARM: the attached example fails on current gcc trunk.
>>
>> panda-9:~ $ g++ segv.cc -fnon-call-exceptions -g
>> panda-9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/28/11 22:02, Jon Masters wrote:
> On Tue, 2011-08-23 at 17:11 +0100, Steve McIntyre wrote:
>
>> UPDATE: we've not had many people confirm interest in this event
>> yet, which is a shame. If you would like to join us for this
>> session, please r
On 08/25/2011 02:26 PM, Andrew Haley wrote:
Throwing an exception through a segfault handler doesn't always work
on ARM: the attached example fails on current gcc trunk.
panda-9:~ $ g++ segv.cc -fnon-call-exceptions -g
panda-9:~ $ ./a.out
terminate called after throwing an instance of 'FoobarExc
Mikael Pettersson writes:
> I'm seeing what appears to be a recent massive performance regression
> with trunk's gengtype, as compiled and run in stage 2, on ARM V5TE.
>
> Right now 4.7-20110827's stage2 gengtype has been running for almost
> 10 hours on my ARM build machine, but the process
