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]
Other format: [Raw text]

Re: Fix c++ ABI failures


   From: Jakub Jelinek <jakub@redhat.com>
   Date: Tue, 30 Apr 2002 18:17:59 -0400

   I think the ChangeLog entry should be marked with `ABI change'
   like other ABI changes were.

I will fix this.  I was not aware of this convention, sorry.

   Still, the question is how should be classes with non-trivial constructors or
   destructors passes on sparc64, ia64 and other ABIs which pass records in
   registers.

   It is clear that such classes have to be passed somewhere in memory, but
   some ABIs might want to promote them into registers in some cases
   and/or pass them in some particular memory slot as opposed to passing them
   by invisible reference.

Mark told me that other ABIs "don't matter".  We need only be
consistent with what we've defined for g++.

I think we should behave sanely with what we have now in the
3.1 branch.


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