From mint-bounce@lists.fishpool.fi  Thu Feb 14 10:01:31 2008
X-Virus-Scanned: amavisd-new at demon.co.uk
Subject: Re: [MiNT] Binutils 2.18 + GCC 4.2.3
From: Alan Hourihane <alanh@fairlite.demon.co.uk>
To: MiKRO <miro.kropacek@gmail.com>
Cc: Keith Scroggins <kws@radix.net>,
        Vincent =?ISO-8859-1?Q?Rivi=E8re?= <vincent.riviere@freesbee.fr>,
        mint <mint@fishpool.com>
In-Reply-To: <c6533ef60802140628m197476a5m550144bb46410bd5@mail.gmail.com>
References: <c6533ef60802051618w1ee05126sf66358ac67512dfc@mail.gmail.com>
	 <c6533ef60802060644m3a97addfp6ffdb388e2300c27@mail.gmail.com>
	 <Pine.GSO.4.63.0802061156430.15097@saltmine.radix.net>
	 <c6533ef60802070129oc4a3dedtfb9b6380cd7c155f@mail.gmail.com>
	 <c6533ef60802080114s7e6430f6n1efc9c681849fb84@mail.gmail.com>
	 <Pine.GSO.4.63.0802081252560.26309@saltmine.radix.net>
	 <c6533ef60802090819u6ffb7b55ha39cfaeafe6b1a16@mail.gmail.com>
	 <47ADDBA8.3050603@freesbee.fr>
	 <Pine.GSO.4.63.0802091216540.15237@saltmine.radix.net>
	 <1202998885.30348.8.camel@localhost>
	 <c6533ef60802140628m197476a5m550144bb46410bd5@mail.gmail.com>
Content-Type: text/plain
Date: Thu, 14 Feb 2008 14:54:18 +0000
Message-Id: <1203000858.30348.11.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: alanh@fairlite.demon.co.uk
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

On Thu, 2008-02-14 at 15:28 +0100, MiKRO wrote:
>  
>         I managed to reproduce this problem here, and reverting
>         MiKRO's patch to
>         startup/crt0.S fixed the problem here.
> But be careful -- the original reason why I make this change was the
> strange behaviour with this premilitary stack -- so I choose to use
> end_of_bss + fixed value instead of memtop.

But for me, your patch is making the situation worse, not better.

So, there must be a "correct" fix.

Can you produce a sample application that demonstrates a problem with
the original crt0.S ?? 

I think it'll be easier to debug if we have an application that does
this first.

Alan.