From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Cc: Bernd Schmidt <bernds_cb1@t-online.de>, Jie Zhang <jzhang918@gmail.com>
Subject: [RFC] slipping in symbol prefixes automagically via PROVIDE() in linker scripts
Date: Sun, 30 Jul 2006 19:45:00 -0000 [thread overview]
Message-ID: <200607301546.08335.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
the blackfin architecture has a symbol prefix of '_' (so in gcc,
__USER_LABEL_PREFIX__ is defined to _) ...
with the old binutils blackfin port (2.15), there is a
binutils/ld/scripttempl/bfin.sc which duplicated a lot of stuff from the
normal elf.sc, so adding the _ prefix to symbols was trivial
with the new binutils-2.17, it'd be good to switch to using the generic elf.sc
file ... but this _ prefix is standing in the way ... there seems to be two
ways to deal with this at the moment:
- copy elf.sc to bfin.sc again and just insert the _ symbols as needed
- tweak PROVIDE() to automatically insert a configurable prefix
from what i can tell after reading the ld docs, PROVIDE is generally for
setting up automatic symbol values when referenced via higher level code
(like C) ... so making PROVIDE "smarter" and having it insert the same
prefixes that higher level language parsers seems like a good idea to me :)
thoughts ? am i off base with the PROVIDE() tweak ? other solutions ? is
blackfin eternally screwed and forced to maintain a mostly duplicate elf.sc ?
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2006-07-30 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 19:45 Mike Frysinger [this message]
2006-07-31 10:12 ` Nick Clifton
2006-07-31 10:25 Will Newton
2006-07-31 16:47 ` Mike Frysinger
2006-08-02 9:25 ` Nick Clifton
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=200607301546.08335.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=bernds_cb1@t-online.de \
--cc=binutils@sourceware.org \
--cc=jzhang918@gmail.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).