X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com
Subject: Re: GCC_DRIVER_HOST_INITIALIZATION vs gcc 3.4
Date: Fri, 23 Jan 2004 09:29:47 +0200
User-Agent: KMail/1.6
References: <200401230233 DOT i0N2Xii4025886 AT envy DOT delorie DOT com>
In-Reply-To: <200401230233.i0N2Xii4025886@envy.delorie.com>
Cc: DJ Delorie <dj AT delorie DOT com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200401230929.47137.pavenis@latnet.lv>
Reply-To: djgpp-workers AT delorie DOT com

On Friday 23 January 2004 04:33, DJ Delorie wrote:
> In xm-djgpp.h we define this macro (see below).  Unfortunately, the
> variables it sets have become const in 3.4, so we cannot change them.
> I've build a version both with and without the three assignments, and
> see negligible difference in the search paths (functionally the same,
> without the assignments is more efficient in my case).  The thread
> discussing this is at [1] where it seems the purpose of these
> assignments is efficiency, not always functionality.  I'm
> contemplating just removing these assignments (but leaving in the
> diagnostics).  Can anyone see any functional problems with such a
> change?

Only question:

in which format gcc will output directories list
(e.g: gcc -v ...)  and dependencies (gcc -MD ...). Perhaps it would be
not a good idea to see there for example 
	/dev/env/DJDIR/include/stdio.h
At least I would prefer for example:
	c:/djgpp/include/stdio.h
If this transformation is done somewhere later, then these asignments 
can be removed.

Andris

PS. Are You building native compiler for DJGPP or cross-compiler. What 
additional patches are applied if any.