From: Richard Russell <richard@rtrussell.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Jump table alignment (2.95.2 versus 3.2.3)
Date: Thu, 30 Dec 2004 18:32:00 -0000 [thread overview]
Message-ID: <6.2.0.14.0.20041230182947.01c7d1d0@mail.e7even.com> (raw)
Hello,
I have recently 'upgraded' to 3.2.3 from 2.95.2 (MinGW version)
and I am trying to get it to produce code no larger than its
predecessor. Even with the -Os option it is still generating
object modules somewhat larger than before, and close examination
shows that this is because jump table (dispatch table) entries
are now aligned on 16-byte boundaries rather than 4-bytes with
2.95.2. With large tables this wastes quite a lot of space.
Is there an option which will force gcc 3.2.3 to use 4-byte or
8-byte alignment for jump table entries ?
Richard.
http://www.rtrussell.co.uk/
next reply other threads:[~2004-12-30 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 18:32 Richard Russell [this message]
2004-12-30 23:09 Richard Russell
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=6.2.0.14.0.20041230182947.01c7d1d0@mail.e7even.com \
--to=richard@rtrussell.co.uk \
--cc=gcc-help@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).