From: Robert Bruce <wyvern AT mbay DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Re: NEED HELP WITH GRX
Date: Fri, 17 Mar 2000 20:27:11 -0800
Organization: Posted via Supernews, http://www.supernews.com
Lines: 53
Message-ID: <pv06ds0qo1kgc56j63jakv9q7rj4mqq198@4ax.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000314095102 DOT 4527I-100000 AT is> <38D0C9F8 DOT 40BECC63 AT ujf-grenoble DOT fr> <8aqsuf$42fh4$1 AT fu-berlin DOT de> <38D16047 DOT 3C9F9A95 AT ujf-grenoble DOT fr>
X-Complaints-To: newsabuse AT supernews DOT com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I tried the patches also and ran into the same problem you are seeing,
the solution was obvious after the fact.  If the assembler says it
shouldn't be there then just remove it.  The cause of the problem has
to do with the assembler/compiler automagically tagging the register
as dirty and it apparently resents us trying to tell it what to do in
cases like that.

here is what the working version on my system looks like.
	  : "=r" ((void *)s), "=r" ((void *)d), "=r" ((int)w)/*,"=cx"
(dummy)*/
	  : "0" ((void *)s), "1" ((void *)d), "2" ((int)w), "c"
((int)shift)
	  : "ax"

The "c" also refers to the cx/ecx register so that is all the notice
the compiler wants or needs.

Regards,
Robert E Bruce

Maurice Lombardi <Maurice DOT Lombardi AT ujf-grenoble DOT fr> wrote:

>Dieter Buerssner a écrit :
>> 
>> Maurice Lombardi wrote:
>> 
>> >Well... I have applied the two patches, compiled (no more error message)
>> >and run the tests contained in the grx23/test subdirectory. Three tests
>> >fails with a SIGSEGV error: blittest, curstest, and imgtest. Using rhide
>> >I find that the error in curstest is in the function __GR_shift_scanline
>> >contained in grx23/src/utils/shifscl.c, in the asm section which has
>> >been patched with patgrx23.diff. I cannot say more since I know
>> >absolutely nothing about AT&T assembly syntax. Anybody knows ???
>> 
>> This may be unrelated, but have you also applied the update patches
>> that can be found on the grx home page?
>
>no but applying them changes nothing
>
>> I didn't apply any offical patches to shiftscl.c, but rather tried
>> the patch I append. The test programs you mention seem to work here
>> in a full screen DOS window in 16 color mode (and in other color modes
>> as weel, but I think, then that function won't be used) with the
>> VESA driver. One other change I made, that could be related, is
>> to set the optimization options to -O only (but I kept
>> -fomit-frame-pointer).
>
>OK, It works now with your patch (even with -O6, and 256 or 64k colors), but I
>need to apply the other patches of Ian Miller contained in patgrx23.diff and
>grx23asm.diff referred to in the DJGPP FAQ (8.17) (otherwise it does not
>compile).
>Thanks !