This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [lto][patch] Patch to fix multiple C++ streaming issues and a residual problem with preload_common_nodes
- From: "Bill Maddox" <maddox at google dot com>
- To: "Diego Novillo" <dnovillo at google dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 1 Aug 2008 12:20:07 -0700
- Subject: Re: [lto][patch] Patch to fix multiple C++ streaming issues and a residual problem with preload_common_nodes
- References: <8a0e66f0807292032p130bfcddw88fc74ea83f8bc50@mail.gmail.com> <b798aad50808010621t3c2d16b4td0cf16c3743b8555@mail.gmail.com>
On Fri, Aug 1, 2008 at 6:21 AM, Diego Novillo <dnovillo@google.com> wrote:
> On Tue, Jul 29, 2008 at 23:32, Bill Maddox <maddox@google.com> wrote:
>> @@ -2756,7 +2812,9 @@ output_namespace_decl (struct output_blo
>> output_tree (ob, decl->decl_common.abstract_origin);
>>
>> gcc_assert (decl->decl_common.mode == 0);
>> - gcc_assert (decl->decl_common.align == 1);
>> + /* FIXME lto: I'm seeing both 0 and 1 here, but I don't
>> + think it is meaningful. Verify this. */
>> + /*gcc_assert (decl->decl_common.align == 1);*/
>
> The alignment is in principle an arbitrary number of bits. We
> should not assert anything here.
What is the significance of DECL_ALIGN in a NAMESPACE_DECL?
--Bill