public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Gcc-mcore -O3?
@ 2001-01-17 16:42 Yanbo Zhou
  0 siblings, 0 replies; 2+ messages in thread
From: Yanbo Zhou @ 2001-01-17 16:42 UTC (permalink / raw)
  To: 'nickc@redhat.com'; +Cc: 'gcc-help@gcc.gnu.org'

Hi Nick,

Me again. You are the expert of GCC for MCore. Can I have your help again?

When I compile several c modules and run on the MCore EVB with "-g -c",
everything is OK. But, when I apply "-c -O3" on the same files, the
activities
become unpredictable. I don't know why? Please help me.

Thank you.

Yanbo ZHOU, Ph.D.
Image Processing Engineer
mailto:yzhou@silent-witness.com

Silent Witness Enterprises LTD.
http://www.silent-witness.com
6554 176th Street
Surrey, BC. V3S 4G5
Canada
Tel: 604-574-1526 ext 8654
Fax: 604-5747736


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Gcc-mcore -O3?
@ 2001-01-18 20:29 Nick Clifton
  0 siblings, 0 replies; 2+ messages in thread
From: Nick Clifton @ 2001-01-18 20:29 UTC (permalink / raw)
  To: yzhou; +Cc: gcc-help

Hi Yanbo,

: Me again. You are the expert of GCC for MCore. Can I have your help
: again?

Sure, send $5 in unmarked bills to.... :-)

: When I compile several c modules and run on the MCore EVB with "-g
: -c", everything is OK. But, when I apply "-c -O3" on the same files,
: the activities become unpredictable. I don't know why? Please help
: me. 

This is probably due to a bug in the MCore port.  Most likely an
optimisation is being performed that is generating incorrect code.
Without any more information I cannot narrow down the source of the
problem.

Here are some things you can try, in order to help locate the problem:

  * Does the problem occur at -O2 ?  How about -Os ?

  * Are there any other switches that you are passing to gcc ?
    If so, does the problem go away when you remove them from the
    command line ?

  * Does the problem still occur if you add the -g flag to gcc's
    command line, in order to enable debugging ?  If so, then cvan you
    use a debugger to narrow down where this unpredictable behavior
    is occurring ?

  * Can you create a small, reproducible test case that demonstrates
    the problem ?  If so, if you past that test case to the list,
    along with instructions on how to make the problem happen, then
    other people can have a go at tracking down the bug.

  * Does the problem happen in the simulator as well as on the
    hardware ?  can you use the instruction tracing feature of the
    simulator to track down where the misbehavior occurs ?

Cheers
	Nick

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-01-18 20:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-17 16:42 Gcc-mcore -O3? Yanbo Zhou
2001-01-18 20:29 Nick Clifton

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).