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: DATA_ALIGNMENT vs. DECL_USER_ALIGNMENT


    I definitely think the bug is *not* in varasm.c.  If I write
    "double x __attribute__((aligned(1)))", I expect to see 

        .comm   x,8,1
    not
	.comm	x,8,8

    in the assembly file.

of course.  That's because in this case you are setting the alignment
of the *object*, not the *type*.

    I definitely think there's a bug in that the Ada front end sets
    DECL_USER_ALIGN for these objects and the C front end (in response to
    the auto-generated files) does not.  That mis-match should be
    addressed in some way -- either by not setting DECL_USER_ALIGN in Ada

But it *isn't* set in Ada! 


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