Re: Broken private gcc port

Il 11/04/2013 15:23, Amir Gonnen ha scritto: > Here it is (also copied back the comment from the original patch): > > @@ -3207,9 +3207,14 @@ > DF_REF_REG_USE, bb, insn_info, flags); > df_uses_record (collection_rec, &XEXP (dst, 2), > DF_REF_REG_USE, bb, insn_info, flags); > + > + /* Handle t

Re: Broken private gcc port

Here it is (also copied back the comment from the original patch): @@ -3207,9 +3207,14 @@ DF_REF_REG_USE, bb, insn_info, flags); df_uses_record (collection_rec, &XEXP (dst, 2), DF_REF_REG_USE, bb, insn_info, flags); + + /* Handle the case of zero_extract(mem(...)) in the set dest. + This s

Re: Broken private gcc port

Il 11/04/2013 14:57, Amir Gonnen ha scritto: > Hi Paolo, > > About 3 years ago I've sent a patch which was submitted by Kenneth > Zadeck on revision 153924 (See > http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00232.html) > > Recently we tried to update our gcc port from gcc-4.4 to gcc-4.8 and > di

Broken private gcc port

Hi Paolo, About 3 years ago I've sent a patch which was submitted by Kenneth Zadeck on revision 153924 (See http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00232.html) Recently we tried to update our gcc port from gcc-4.4 to gcc-4.8 and discovered that the same lines of code were changed, thus break