From: Nathan Sidwell <nathan@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: mark@codesourcery.com, jason@redhat.com
Subject: Killing old abi remnants
Date: Wed, 18 Jul 2001 07:46:00 -0000 [thread overview]
Message-ID: <3B55A14A.1281CED8@codesourcery.com> (raw)
Hi,
We have old & new abi code in the compiler. This is selected via the
following #defines
#define vbase_offsets_in_vtable_p() (1)
#define vcall_offsets_in_vtable_p() (1)
#define vptrs_present_everywhere_p() (1)
#define all_overridden_vfuns_in_vtables_p() (1)
#define merge_primary_and_secondary_vtables_p() (1)
will a patch which removes all old abi remnants be acceptable?
As time progresses those old abi parts are going to suffer bitrot.
and what about flag_honor_std?
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2001-07-18 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 7:46 Nathan Sidwell [this message]
2001-07-18 8:06 ` Joseph S. Myers
2001-07-18 9:13 ` Mark Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B55A14A.1281CED8@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mark@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).