http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59083
Markus Trippelsdorf <octoploid at yandex dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |octoploid at yandex dot com
--- Comment #4 from Markus Trippelsdorf <octoploid at yandex dot com> ---
(In reply to Jeffrey A. Law from comment #2)
> I need a compilable/complete testcase.
>
> If a program is faulting with -fisolate-erroneous-paths, then that program
> is faulty in one way or another. It's dereferencing a null pointer, pass a
> null argument in a situation where the argument must be non-null, or
> returning a null pointer from a function declared as returning non-null.
I'm seeing this also quite often. Xorg fails to start when
compiled with current gcc, the Linux kernel doesn't build, because
relocs (build during the kernel build) fails with illegal instruction,
etc..
So tbe -fisolate-erroneous-paths patch should be reverted IMHO.
