From: Olivier Hainque <hainque@adacore.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: gcc@gcc.gnu.org, hainque@adacore.com
Subject: Re: BIGGEST_ALIGNMENT vs g++ compat test expectation on aix ?
Date: Thu, 02 Jul 2009 16:49:00 -0000 [thread overview]
Message-ID: <20090702164924.GB28857@cardhu.act-europe.fr> (raw)
In-Reply-To: <303e1d290906300722p49fb56f2w87915994935a0b9b@mail.gmail.com>
David Edelsohn wrote:
> > Â Â Â Â .csect .data[RW],4
> > Â Â Â Â Â Â Â Â Â Â Â Â ^^^
> > Â Â Â Â .align 6
> > Â Â Â Â Â Â Â ^^^
> > a2661:
> > Â Â Â Â .space 10240
>
> The default alignment of CSECTs is 4, but using -fdata-sections should
> place the object in its own CSECT with stricter alignment.
Humm, it apparently doesn't: I see no difference in the generated
assembly for t027_y.C.
Olivier
prev parent reply other threads:[~2009-07-02 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:10 Olivier Hainque
2009-06-30 15:14 ` David Edelsohn
2009-07-02 16:49 ` Olivier Hainque [this message]
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=20090702164924.GB28857@cardhu.act-europe.fr \
--to=hainque@adacore.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).