This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ia64 crtbegin/end changes


I wasn't able to reproduce this problem.  I've got an unpatched gcc tree,
with a reasonably up-to-date binutils, on a system running the May 17 Red Hat
ia64-linux OS release.

The testcase you mention g++-jason/ctors1.C doesn't actually have any ctors.
You can see that the first element of the __CTOR_LIST__ is -1, and __CTOR_END__
is __CTOR_LIST__ + 8.  loc0/r32 should have the value of &__CTOR_LIST__ after
the first load instruction.  The next load then puts -1 in loc3/r35, and the
branch should be taken.  This is what I am seeing.

Jim

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]