From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1504 invoked by alias); 12 Apr 2005 20:22:37 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 996 invoked from network); 12 Apr 2005 20:22:27 -0000 Received: from unknown (HELO kluster2.contactor.se) (193.15.23.26) by sourceware.org with SMTP; 12 Apr 2005 20:22:27 -0000 Received: from [127.0.0.1] (linux3.contactor.se [193.15.23.23]) by kluster2.contactor.se (8.12.3/8.12.3/Debian-7.1) with ESMTP id j3CKMQve027764 for ; Tue, 12 Apr 2005 22:22:27 +0200 Message-ID: <425C2E3B.9050708@haxx.se> Date: Tue, 12 Apr 2005 20:22:00 -0000 From: Linus Nielsen Feltzing User-Agent: Debian Thunderbird 1.0 (X11/20050116) MIME-Version: 1.0 To: binutils@sources.redhat.com Subject: Re: Why no expressions in MEMORY command? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg00294.txt.bz2 Dave Korn wrote: > FYI: I looked into it in some depth once; it would require quite a hefty > bit of patching, since the information about symbol values isn't evaulated > yet at the time the parser is reading the MEMORY command. In the Rockbox project, we use the C preprocessor on the linker command files. That way we can use #define, #ifdef and so on. Very useful. Linus