Re: Patches to fix GCC’s C++ exception handling on NetBSD/VAX

2016-03-26 Thread Jake Hamby
Unfortunately, my previous patch that included a change to gcc/config/vax/vax.h that increased FIRST_PSEUDO_REGISTER from 16 to 17 breaks the C++ exception handling that I’d worked so hard to get right with the rest of the patch. I believe I need to define DWARF_FRAME_REGISTERS to 16 in the same

Re: Patches to fix GCC’s C++ exception handling on NetBSD/VAX

2016-03-26 Thread Jake Hamby
As an added bonus, I see that my patch set also included an old m68k patch that had been sitting in my tree, which fixes a crash when -m68040 is defined. I may have submitted it to port-m68k before. It hasn’t been tested with the new compiler either. Here’s that patch separately. It only matter

Re: Patches to fix GCC’s C++ exception handling on NetBSD/VAX

2016-03-26 Thread Jake Hamby
> On Mar 23, 2016, at 05:56, Christos Zoulas wrote: > > In article , > Jake Hamby wrote: > > Hi, > > Thanks a lot for your patch. I applied it to our gcc-5 in the tree. > Unfortunately gcc-5 seems that it was never tested to even compile. > I fixed the simple compilation issue, but it fails t

Re: C++ PATCH for c++/70353 (core issue 1962)

2016-03-26 Thread Markus Trippelsdorf
On 2016.03.25 at 17:29 -0400, Jason Merrill wrote: > 70353 is a problem with the function-local static declaration of __func__. > Normally constexpr functions can't have local statics, so this is only an > issue with __func__. Meanwhile, core issue 1962 looks like it's going to be > resolved by ch

Re: C++ PATCH for c++/70353 (core issue 1962)

2016-03-26 Thread Dominique d'Humières
Hi Jason, The following tests for g++.dg/ext/fnname5.C fail on darwin FAIL: g++.dg/ext/fnname5.C -std=c++11 scan-assembler .string\\t"foo" FAIL: g++.dg/ext/fnname5.C -std=c++11 scan-assembler .string\\t"void A::foo(int)" FAIL: g++.dg/ext/fnname5.C -std=c++14 scan-assembler .string\