This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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: [PATCH] Pad SEC_MERGE sections to entsize boundary in gas


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jakub Jelinek wrote:

>>This is presumably just due to lack of alignment padding after the
>>last entry, right?  Otherwise the merge code would be rather
>>confused...
> 
> 
> Yeah. gcc emits something like:
>         .section        .rodata.cst16,"aM",@progbits,16
>         .align 16
> .LC0:
>         .long   0
>         .long   -939524096
>         .long   16389
> for long double constants and doesn't put there another .align 16
> after it (or another .long 0).

I actually believe it is gcc's fault.

Why should every entry in a .rodata.cst16 section have .align 16?
Alignment and size are two different issues.

gcc should emit the padding word, too.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE94eIG2ijCOnn/RHQRAuLFAKCSVZfi4W0Z1ZZ8htcilAT8AbnSTACeJ3l0
uthn9FH5N9vBJ3KDkdclZa4=
=v4dK
-----END PGP SIGNATURE-----


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