Date:	Mon, 21 Feb 2000 19:26:18 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Message-Id:	<200002211726.TAA10841@is.elta.co.il>
To:	djgpp-workers AT delorie DOT com
CC:	Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
In-reply-to:	<200002171707.SAA16280@cerbere.u-strasbg.fr> (message from Pierre
	Muller on Thu, 17 Feb 2000 17:53:09 +0100)
Subject:	Re: Bug in crt0.S
References:	<200002171707 DOT SAA16280 AT cerbere DOT u-strasbg DOT fr>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

>   I include here a diff to version 2.03 of crt0.S file that also fixes the
> problem for the C library!

Pierre, I don't understand this patch: it seems that you store
something in sbrk16_interrupt_state, but never use that value:

> *** 552,557 ****
> --- 567,576 ----
>   	movw	___djgpp_base_address+2, %cx
>   	int	$0x31
>   
> +    /* Now we can reenable interrupts  PM */
> +    movl  %eax,sbrk16_interrupt_state
> +    int   $0x31
> +    

Shouldn't this be the other way around: "movl sbrk16_interrupt_state,%eax"?

- Raw text -