From: dewar@gnat.com
To: aoliva@redhat.com, gcc@gcc.gnu.org
Subject: Re: C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT
Date: Fri, 06 Apr 2001 03:34:00 -0000 [thread overview]
Message-ID: <20010406103405.A1026F28E7@nile.gnat.com> (raw)
are there really architectures where there is no penalty for having
odd-aligned function addresses? Hard to believe! Of course there are
architectures where there is no *hard requirement* for alignment, but
one would almost certainly expect a performance penalty. On the x86
for example, it is quite important to give decent alignment to jump
targets from an efficiency point of view.
next reply other threads:[~2001-04-06 3:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 3:34 dewar [this message]
2001-04-06 4:41 ` Jamie Lokier
2001-04-06 6:02 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2001-04-06 5:05 dewar
2001-04-06 5:10 ` Jamie Lokier
2001-04-06 4:49 dewar
2001-04-06 5:00 ` Alexandre Oliva
2001-04-06 3:14 Alexandre Oliva
2001-04-06 10:53 ` Neil Booth
2001-04-06 11:03 ` Alexandre Oliva
2001-04-07 4:52 ` Richard Earnshaw
2001-04-07 10:12 ` Dave Korn
2001-04-06 13:05 ` Jim Wilson
2001-04-06 14:45 ` DJ Delorie
2001-04-09 8:19 ` Alexandre Oliva
2001-04-09 12:28 ` Joern Rennecke
2001-04-09 13:12 ` Alexandre Oliva
2001-04-09 13:43 ` Joern Rennecke
2001-04-18 5:48 ` Richard Earnshaw
2001-04-18 12:11 ` Alexandre Oliva
2001-04-10 9:27 ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 *BITS_PER_UNIT Mark Mitchell
2001-04-17 10:38 ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT Andrew Cagney
2001-04-17 13:02 ` Daniel Berlin
2001-05-16 4:53 ` Jason Merrill
2001-05-16 7:18 ` Daniel Berlin
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=20010406103405.A1026F28E7@nile.gnat.com \
--to=dewar@gnat.com \
--cc=aoliva@redhat.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).