[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2014-04-03 Thread charles.baylis at linaro dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

Charles Baylis charles.baylis at linaro dot org changed:

   What|Removed |Added

 CC||charles.baylis at linaro dot 
org

--- Comment #25 from Charles Baylis charles.baylis at linaro dot org ---

I have proposed a fix for this:

http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00078.html


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2014-01-20 Thread y.gribov at samsung dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

Yury Gribov y.gribov at samsung dot com changed:

   What|Removed |Added

 CC||y.gribov at samsung dot com

--- Comment #21 from Yury Gribov y.gribov at samsung dot com ---
Can we accept Julian's patch for 4.9? This bug really hurts.


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2014-01-20 Thread ebotcazou at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

--- Comment #22 from Eric Botcazou ebotcazou at gcc dot gnu.org ---
IMO this bug should be moved to P1 as a regression on a primary platform and
the RMs should up the pressure on the maintainers to have it fixed.


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2014-01-20 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

--- Comment #23 from Jakub Jelinek jakub at gcc dot gnu.org ---
IMHO a bug that is known for 2.5 years and unfixed shouldn't be all of sudden
P1.  That doesn't mean the maintainers should ignore the bug, just that it
isn't a release blocker.


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2014-01-20 Thread ebotcazou at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

--- Comment #24 from Eric Botcazou ebotcazou at gcc dot gnu.org ---
 IMHO a bug that is known for 2.5 years and unfixed shouldn't be all of
 sudden P1.  That doesn't mean the maintainers should ignore the bug, just
 that it isn't a release blocker.

I'm afraid that history has shown that you won't achieve the former without
doing the latter...


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2013-06-20 Thread jules at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423

jules at gcc dot gnu.org changed:

   What|Removed |Added

 CC||jules at gcc dot gnu.org

--- Comment #20 from jules at gcc dot gnu.org ---
I've posted a new potential fix (and a new testcase which breaks on current
mainline) here:

http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01191.html


[Bug target/49423] [4.7/4.8/4.9 Regression] [arm] internal compiler error: in push_minipool_fix

2013-04-12 Thread jakub at gcc dot gnu.org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423



Jakub Jelinek jakub at gcc dot gnu.org changed:



   What|Removed |Added



   Target Milestone|4.6.4   |4.7.4



--- Comment #19 from Jakub Jelinek jakub at gcc dot gnu.org 2013-04-12 
15:16:21 UTC ---

GCC 4.6.4 has been released and the branch has been closed.