This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: FW: Bug in cc1 - wrong/incosistent code
- To: IlanM at bvr dot co dot il, gcc-bugs at gcc dot gnu dot org
- Subject: Re: FW: Bug in cc1 - wrong/incosistent code
- From: Mike Stump <mrs at windriver dot com>
- Date: Mon, 6 Mar 2000 14:44:31 -0800 (PST)
- Cc: irit dot mano at nsc dot com
> From: Ilan Mano <IlanM@bvr.co.il>
> To: "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>
> Cc: "'irit.mano@nsc.com'" <irit.mano@nsc.com>
> Date: Mon, 6 Mar 2000 16:38:56 +0200
> I'm developing a GCC based cross-compiler for our CompactRISC family of
> 16-bit processors. The bug described below occured on our modified compiler
> which includes many changes from the original GCC sources that I cannot list
> here, but I believe that the bug is not induced by these changes. I'm
> including assembly code for our architecture, which I believe is
> straighforward enough to understand.
You should work on getting your changes submitted back and getting
your port included in gcc. This will simplify your life, and ours.
> GCC version: 2.95.1 + hand merging of 2.95.2 changes Input file:
> int *pa;
> void f()
> {
> *(pa++) = *(pa++) + *(pa++);
> }
> Command arguments: -O
> Operating system: Windows NT, using MSVC cl compiler.
> Bug description:
> The compiler generates for the source code above functionally
> different code when compiled with -O and withou it, and both outputs
> are functionally different from the code generated by our GCC 2.7.2
> based compiler.
I think you need to go back and re/read that C book you bought. This
isn't a bug in the compiler. This stuff is kinda basic. If you want
to learn C, please try comp.lang.c before this forum, thanks.