Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 21 Dec 2002 12:19:52 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com, Binutils Subject: Re: [PATCH] exclude runtime-pseudo-reloc symbols from auto-export Message-ID: <20021221171952.GA22113@redhat.com> Reply-To: cygwin AT cygwin DOT com, binutils AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT cygwin DOT com, Binutils References: <1040456890 DOT 7654 DOT 1 DOT camel AT lifelesswks> <012101c2a8f2$4ef75820$0a1c440a AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012101c2a8f2$4ef75820$0a1c440a@BRAMSCHE> User-Agent: Mutt/1.5.1i On Sat, Dec 21, 2002 at 02:10:18PM +0100, Ralf Habacker wrote: >>>Maybe the horse has left the barn already but it would have been nice >>>(tm) if these type of symbols were marked in some generic way so that >>>we wouldn't have to keep remembering to extend this table. >> >>I recall commenting on this aspect in a recent binutils thread in the >>cygwin lists, and being told that it didn't matter. >> >What about putting such symbols in another named text section, so that >ld would ignore them ? I don't see how you could do that since the symbol is associated with an existing place in memory. We could put the whole function in a different segment but that's not the kind of solution I was thinking of. I was thinking that there might be an unused attribute that could be pressed into service as a "don't auto export" (doesn't linux/elf have something like this?) or that there was a way to name the symbol in some way that wasn't easily available from a C program, like putting a "." in the name with an asm alias. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/