On 08/23/2016 10:54 AM, Jonathan Wakely wrote:
>> That's being set by prettyprinters.exp and xmethods.exp (so it's GDB's
>> fault! ;-)
:-)
> This seems to work. I'll do some more testing and commit later today.
LGTM.
Though IME, save/restoring globals in a constant source of trouble,
for occa
On 23/08/16 09:07 +0100, Jonathan Wakely wrote:
On 22/08/16 21:16 +0100, Pedro Alves wrote:
On 08/22/2016 03:40 PM, Jonathan Wakely wrote:
What's going on?!
Have I fundamentally misunderstood something about how RUNTESTFLAGS or
effective-target keywords work?
Here's a wild guess.
In gdb's
On 22/08/16 21:16 +0100, Pedro Alves wrote:
On 08/22/2016 03:40 PM, Jonathan Wakely wrote:
What's going on?!
Have I fundamentally misunderstood something about how RUNTESTFLAGS or
effective-target keywords work?
Here's a wild guess.
In gdb's testsuite, I've seen odd problems like these bei
On 08/22/2016 03:40 PM, Jonathan Wakely wrote:
> What's going on?!
>
> Have I fundamentally misunderstood something about how RUNTESTFLAGS or
> effective-target keywords work?
>
Here's a wild guess.
In gdb's testsuite, I've seen odd problems like these being caused by some
tcl global getting s
I'm confused by what I'm seeing when running the libstdc++ tests with:
RUNTESTFLAGS='--target_board=\"unix{-std=gnu++98,-std=gnu++11,-std=gnu++14,-std=gnu++17}\"'
If I inspect the libstdc++.sum file to look for the results for a
particular file that has { dg-do compile { target c++14 } }, I find
