This is the mail archive of the
mailing list for the GCC project.
Re: vtables patch 1/3: allow empty array initializations
- From: Mike Stump <mikestump at comcast dot net>
- To: Bernd Schmidt <bernds at codesourcery dot com>
- Cc: DJ Delorie <dj at redhat dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 28 Apr 2013 12:36:37 -0700
- Subject: Re: vtables patch 1/3: allow empty array initializations
- References: <5177BBB8 dot 1070901 at codesourcery dot com> <201304241510 dot r3OFA4qj010017 at greed dot delorie dot com> <51780D8C dot 4060405 at codesourcery dot com> <201304241914 dot r3OJE1kw016932 at greed dot delorie dot com> <517A5F96 dot 5090804 at codesourcery dot com>
On Apr 26, 2013, at 4:05 AM, Bernd Schmidt <email@example.com> wrote:
> On 04/24/2013 09:14 PM, DJ Delorie wrote:
>>> 24 bits stored as three bytes, or four? How does this affect vtable
>>> layout? I would have expected the C++ frontend and libsupc++ to
>>> currently be inconsistent with each other given such a setup.
>> In memory, four, I think. The address registers really are three
>> bytes though. They're PSImode and gcc doesn't really have a good way
>> of using any specified PSImode precision.
I have patches to let one specify a precision for partial int types, easy enough to do, and the rest of the compiler plays nicely for the most part with it...