X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <52ADA6C1.2050209@gmx.de> Date: Sun, 15 Dec 2013 13:55:29 +0100 From: Juan Manuel Guerrero User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: Watt32 crashing on i386 References: <52a72357$0$3635$426a74cc AT news DOT free DOT fr> <8ab75766-10f6-4999-bd48-34e812c6c3bd AT googlegroups DOT com> <52ad7122$0$2914$426a34cc AT news DOT free DOT fr> In-Reply-To: <52ad7122$0$2914$426a34cc@news.free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ybZFuMXt3EIN+xWY8yGcdG2uh/6Fj0XNf1GFV5ArV9nTa6Bqyo+ BJNBN46FfHhfU+TKWfN9P+4WzPr0OX7A6SQ++3yX0yyeK3iBRfwrtVSDsw2L3kchjIkYrGS wsKUOa5ClIbnUl7gPLifKaYE03qno7WcSjGX7EYrWgYGY8xWV3eiAmPO8K/NlqhCaFG9c4f XGTI5K+KaW76BfYzJC3+w== Reply-To: djgpp AT delorie DOT com Am 15.12.2013 10:06, schrieb Mateusz Viste: > Hi, > > Just to say thanks :) The latest "386libwatt" port you did recently works fine on a pre-pentium machine. I see it wasn't enough to just recompile it with -march=i386 as I did it, because watt32 itself seems to be buggy itself in regard of older (386/486) CPUs... Thanks! > > I am still not sure however about the need of compiling it under an older gcc.. What makes me wonder, is that I use the stock gcc as packaged with DJGPP 2.03 (gcc v4.7.1), I compile my program with it (just passing -march=i386), and still it works fine on old CPUs.. Is there any way I could verify myself the opcodes present in a binary file outputted by DJGPP (other than analyzing it for hours in a debugger of course)? > > cheers, > Mateusz > > > I do not know if it is really necessary to use a pre gcc4NN compiler to get clean 386 code. I simply wanted to be sure that to code was OK, so I used the oldest compiler from the /beta directory (DJGPP 2.04). Feel free to recompile the sources using gcc 4.7.1 together with -march=i386 and see what happens. Anyway you are the only one that can check if your application works on i386/i486 hardware. I no longer have access to this type of computer. I am not familiar enough with gcc to tell you if there is a way to certainly determinate if a gcc version is still able to generate clean 386 code. Ask Andris or ask the on a gcc mailing list directly. Regards, Juan M. Guerrero