public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Need advice on DEFAULT_VTABLE_THUNKS settings
@ 2000-05-26 21:03 David O'Brien
  2000-05-27  0:43 ` Martin v. Loewis
  0 siblings, 1 reply; 2+ messages in thread
From: David O'Brien @ 2000-05-26 21:03 UTC (permalink / raw)
  To: gcc

In the gcc-2_95-branch vtable-thunks has changed such that it takes a
"version" number.  In FreeBSD 4.0-RELEASE I turned DEFAULT_VTABLE_THUNKS
off due to the bugs present with it.  For compatibility to the 4.x, I
think freebsd-elf.h should leave DEFAULT_VTABLE_THUNKS undefined.

What is the relationship to -vtable-thunks=3 and the C++ ABI in 2.96/3.0?
In the FreeBSD -CURRENT development should I move towards
"DEFAULT_VTABLE_THUNKS 3" or not use thunks at all?  I really do not want
to break compatibility in the 4.x versions, but I can in the 5.0
development.

-- 
-- David    (obrien@NUXI.com)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Need advice on DEFAULT_VTABLE_THUNKS settings
  2000-05-26 21:03 Need advice on DEFAULT_VTABLE_THUNKS settings David O'Brien
@ 2000-05-27  0:43 ` Martin v. Loewis
  0 siblings, 0 replies; 2+ messages in thread
From: Martin v. Loewis @ 2000-05-27  0:43 UTC (permalink / raw)
  To: obrien; +Cc: gcc

> What is the relationship to -vtable-thunks=3 and the C++ ABI in 2.96/3.0?

It is a completely different thing. -fvtable-thunks=2/3 fixes a
long-standing bug in the vtable thunks implementation; gcc 3 won't use
vtable thunks anymore (at least not in the way that caused this bug).

Regards,
Martin

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-05-27  0:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-26 21:03 Need advice on DEFAULT_VTABLE_THUNKS settings David O'Brien
2000-05-27  0:43 ` Martin v. Loewis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).