https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231
--- Comment #13 from manfred.rudigier at omicron dot at ---
(In reply to Dan Wilder from comment #12)
> I have a backport of the patches referenced in comment 4, which I applied to
> the gcc-4.8.3 we are using for e500v2. If anybody woul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231
--- Comment #8 from manfred.rudigier at omicron dot at ---
(In reply to Jakub Jelinek from comment #7)
> GCC 4.8.4 has been released.
I have tried out GCC 4.8.4 today, but it still has this issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231
--- Comment #3 from manfred.rudigier at omicron dot at ---
I was probably to enthusiastic, the problem is still there, even in GCC 4.9.2.
In order to reproduce the bug, you either have to use a root file system which
was also built with GCC 4.8.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231
--- Comment #2 from manfred.rudigier at omicron dot at ---
I've built 4.9.2 today and can also confirm that it is working with this
version, so it seems the bug has already been fixed in newer GCC versions.
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: manfred.rudigier at omicron dot at
Problem:
The GCC exception handling mechanism for powerpc-e500v2-linux-gnuspe seems to
be broken. Every programs abort as soon as the first