From:	rlyon01 AT ozemail DOT com DOT au (Richard Lyon)
Subject:	Re: EGCS Optimisation??
16 Dec 1998 17:32:59 -0800 :
Message-ID:	<000001be28f0$12e0ff70$69536ccb.cygnus.gnu-win32@rlyon>
Mime-Version:	1.0
To:	"Mumit Khan" <khan AT xraylith DOT wisc DOT edu>
Cc:	<gnu-win32 AT cygnus DOT com>

Yes I will do these things. I don't want anyone to waste time if there isn't
a 'real' problem.

It is fantastic to have the simulator running under NT. We are hoping to
make cygwin the preferred port for omnetpp. My university is beginning to
adopt omnetpp in preferance to opnet. Having cygwin available makes it
feasible for students to run omnetpp without having to buy another compiler.

I enjoy using cygwin and are most impressed.

-----Original Message-----
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
To: Richard Lyon <rlyon01 AT ozemail DOT com DOT au>
Cc: gnu-win32 AT cygnus DOT com <gnu-win32 AT cygnus DOT com>
Date: Tuesday, 15 December 1998 17:28
Subject: Re: EGCS Optimisation??


>"Richard Lyon" <rlyon01 AT ozemail DOT com DOT au> writes:
>> Hi,
>>
>> I am working on porting the omnetpp discrete-event simulator to cygwin.
The
>> port is basically complete, with exception that some of the code won't
>> compile correctly when I turn on compiler optimisations. The simulator
>  ^^^^^^
>  (I'm assuming that you mean execute here).
>
>> startup modules compile and run with option -O0. But, when I turn on the
>> most basic optimisation -O1, the simulator executable dies with a status
>> access violation exception. Quickly checking with gdb, shows that some
code
>> is running which should not be reachable. Manually
>> selecting -fthread-jumps, -fdefer-pop -fomit-frame-pointer doe not causes
>> any problems. I am using 20.1 on winnt 4.0 and SP4.
>>
>> When -O1 is selected, what other optimisations are turned on? The gcc
info
>> pages do not specify all
>> optimisations that are activated by -O1.
>
>There is always the chance that you're tweaking a bug in the optimizer,
>but I strongly recommend that you first run your code through a memory
>debugger (Purify is what I use, but ElectricFence can also help find most
>of the usual problems) first.
>
>If that doesn't show anything in your code, time to file a bug report.
>Please see http://egcs.cygnus.com/faq.html#bugreport on how to do so.
>I'll be willing to take a quick look if you can bundle it all up.
>
>Regards,
>Mumit
>
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -