I dont test it ,but I think the
-
__code unsigned char a[4] = {0x12, 0x13, 0x14, 0x15};
shoule be same as:
const unsigned char a[4] = {0x12, 0x13, 0x14, 0x15};
-
Hello,
You should test both ways.
As far as the way your program functions, you are right, both __code and const
will look the same to your program. Both will be constant values that can't be
changed.
Look at the assembly listing and the memory map files. You will see a
difference in the
I'll do what you say. Thanks.
Merry Christmas..:-)
圣诞快乐..
2012/12/24 Rich Bayless
> Hello,
>
> You should test both ways.
>
> As far as the way your program functions, you are right, both __code and
> const will look the same to your program. Both will be constant values
> that can't be
I am getting the errors below when I compile a known working file. (It compiles
fine with Keil.) I suspect the problem is because I need to be running cygwin.
I have installed cygwin but I have no idea how to use it. Can anyone tell me
how to impliment cygwin with my Silab IDE running SDCC??
s
--- On Mon, 12/24/12, iTronix wrote:
From: iTronix
Subject: [Sdcc-user] cygwin??
To: sdcc-user@lists.sourceforge.net
Date: Monday, December 24, 2012, 11:28 AM
I am getting the errors below when I compile a known working file. (It
compiles fine with Keil.) I suspect the problem is because I
When using sdcc with cygwin, I usually compile it and do a make install
in cygwin just as one would on Unices.
Philipp
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile
Hi iTronix,
> sdcpp.exe: fatal error: when writing output to : No error
> at 1: warning 119: don't know what to do with file 'DB'. file extension
> unsupported
> at 1: warning 119: don't know what to do with file 'OE'. file extension
> unsupported
> at 1: warning 119: don't know what to do with
