http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #12 from Anatoly Sinyavin ---
Does it mean that my solution is not accepted?
If it's so I am going to think about two approaches
- vectorizer should ignore that path (Richard Biener 2013-09-09 08:22:53
UTC)
- replacing the GI
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #9 from Anatoly Sinyavin ---
Created attachment 31082
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31082&action=edit
Patch for new solution
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #8 from Anatoly Sinyavin ---
(In reply to Marc Glisse from comment #7)
> (In reply to Anatoly Sinyavin from comment #3)
> > So I suggest processing __builtin_unreachable immediately after "cfg" pass
> > (cfg buiding).
>
> That seems a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57558
Anatoly Sinyavin changed:
What|Removed |Added
CC||a.sinyavin at samsung dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #6 from Anatoly Sinyavin ---
I have created two patches to fix this problem.
The first patch (bug_fix_58359_builit_unreachable.patch) just moves
functionality of optimize_unreachable from "fab" pass to "cfg" pass
The second pat
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #5 from Anatoly Sinyavin ---
Created attachment 30915
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30915&action=edit
Second patch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
--- Comment #4 from Anatoly Sinyavin ---
Created attachment 30914
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30914&action=edit
Fisrt patch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58359
Anatoly Sinyavin changed:
What|Removed |Added
CC||a.sinyavin at samsung dot com
