public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: .text.compat
Date: Wed, 10 Mar 2004 09:36:00 -0000	[thread overview]
Message-ID: <404EE168.2000904@redhat.com> (raw)

I just checked in some changes which move the compatibility code in libc
into its own section, .text.compat.  The linker scripts will add the new
section at the end of the .text section.

The benefit is, of course, to move hopefully rarely used code out of the
usual body of code.  Currently these are about 13k on x86.  It has the
potential to improve paging behavior, maybe even icache usage.

Anyway, I looked through x86 only so far.  Other archs with compat
symbols which are not used by x86 need some work done.  Just add the
attribute_compat_text_section macro.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

             reply	other threads:[~2004-03-10  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  9:36 Ulrich Drepper [this message]
2004-03-10 10:55 ` [PATCH] .text.compat markings Jakub Jelinek
2004-03-10 19:29   ` Ulrich Drepper

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=404EE168.2000904@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /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).