The attachment is a complete patch for [google/gcc-4_6] branch, to
replace .ctors/.dtors with .init_array/.fini_array.
Bootstrap and crosstool testers pass.
I have verified that gcc_cv_initfini_array=no, which means the
crosstool will do whatever it did before (won't replace .ctors/.dtors
with
Hello,
Hey, Jing, you broke the google/gcc-4_6 branch by checking the new
header file into the wrong directory.
Fixed via r184386.
google/gcc-4_6_2-mobile branch still has the same problem. Could
please someone fix it?
Thanks
Ilya
Ollie
On Fri, Feb 17, 2012 at 10:25 PM, Jing Yu
Sorry -- I will fix it in google/gcc-4_6_2-mobile.
Thanks,
Jing
On Mon, Feb 20, 2012 at 7:15 AM, Ilya Enkovich enkovich@gmail.com wrote:
Hello,
Hey, Jing, you broke the google/gcc-4_6 branch by checking the new
header file into the wrong directory.
Fixed via r184386.
Hi H.J.,
I think the patch itself is not enough.
I compared AC_DEFUN([gcc_AC_INITFINI_ARRAY] part (in acinclude.m4)
of gcc trunk and google/gcc-4_6_2-mobile, and found how
enable_initfini_array is
configured is different.
The patch breaks some of our tests. enable_initfini_array should be
Hey, Jing, you broke the google/gcc-4_6 branch by checking the new
header file into the wrong directory.
Fixed via r184386.
Ollie
On Fri, Feb 17, 2012 at 10:25 PM, Jing Yu jin...@google.com wrote:
OK. Thanks for porting the patch.
I will commit the patch into google/gcc-4_6_2-mobile for you.
On Fri, Feb 17, 2012 at 05:20:02PM -0800, H.J. Lu wrote:
This patch backports the fix from trunk:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770
for google/gcc-4_6_2-mobile branch. This is needed to support C++
global constructors/destructiors on Android/x86. OK for
OK. Thanks for porting the patch.
I will commit the patch into google/gcc-4_6_2-mobile for you.
I would also like to commit it into google/gcc-4_6 branch if all tests
pass. This patch is almost the same as Google Ref 47894.
Thanks,
Jing
On Fri, Feb 17, 2012 at 5:20 PM, H.J. Lu
