From: Jeffrey A Law <law@hurl.cygnus.com>
To: Zack Weinberg <zack@rabi.columbia.edu>
Cc: N8TM@aol.com, egcs@egcs.cygnus.com
Subject: Re: ridiculous amounts of padding
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <1760.916370183@hurl.cygnus.com> (raw)
In-Reply-To: <199901150310.WAA23774@rabi.phys.columbia.edu>
In message < 199901150310.WAA23774@rabi.phys.columbia.edu >you write:
> I'm fine with leaving the alignment rules as is for the general case. I
> think it might be a good idea to reduce alignment for the special case of
> many strings allocated next to one another, but I never claimed to be an
> expert in this sort of thing.
First, you can't ever assume that consecutive strings will end up consecutive
in the final image. It's not uncommon for linkers to rearrange stuff in the
data and readonly data segments in an attempt to:
* Delete useless "sethi" type instructions for address calculations on risc
machines
* sort items based on size/alignment needs
> It is unfortunate that Kaveh's idea of collapsing multiple consecutive
> printf/puts calls down to one can't be implemented at the moment. I seem
> to remember someone suggested doing the tree->rtl conversion on a per-block or
> per-function basis to enable more optimization on the trees. Is that a
> non-starter?
It's still a long term goal, but it's not a focus of work at the moment.
jeff
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 N8TM
1999-01-31 23:58 ` Zack Weinberg
1999-01-31 23:58 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-01 17:28 N8TM
1999-02-28 22:53 ` N8TM
1999-01-31 23:58 Zack Weinberg
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Peter Barada
1999-01-31 23:58 ` Zack Weinberg
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Zack Weinberg
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58 ` Nick Ing-Simmons
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` John Vickers
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Alfred Perlstein
1999-01-31 23:58 John Wehle
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58 ` Jeffrey A Law
1999-01-30 16:35 ` Marc Lehmann
1999-01-31 20:05 ` Jeffrey A Law
1999-02-01 8:07 ` Marc Lehmann
1999-02-28 22:53 ` Marc Lehmann
1999-01-31 23:58 ` Marc Lehmann
1999-01-31 23:58 ` David Edelsohn
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Gabriel Dos Reis
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58 John Wehle
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=1760.916370183@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=N8TM@aol.com \
--cc=egcs@egcs.cygnus.com \
--cc=zack@rabi.columbia.edu \
/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).