Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


#2 some comments from jesus

Johan Knol

Just reviewed them. There is a typo in my email. It
should be jesusc@...,
not jesus@... Or even better, the whole credit
paragraph can be
removed! Another thing: in the context of the section, it
should be
mentioned at the beginning that the SDCC source code
is needed first:

"First download and install the source code either from
repository or the nightly snapshot
( SDCC is
distributed with all the

Also in section "3.2 Command Line Options:"

a) All the options require a double dash. For example it
is --stack-loc
not -stack-loc.

b) Recently I added two more link options: --xram-size
and --code-size.
The descriptions are similar to the description of --idata-
size (there is a
typo: 'interal'):

[--xram-size<Value>]Causes the linker to check if the
external ram usage is
within limits of the given value.

[--code-size<Value>]Causes the linker to check if the
code usage is within
limits of the given value.

c) The description for --stack-loc is outdated. One
possibility could be:

By default the stack is placed after the data segment.
Using this option
the stack can be placed anywhere in the internal
memory space of the
8051. The value entered can be in Hexadecimal or
Decimal format, e.g.
--stack-loc 0x20 or --stack-loc 32. Since the sp register
is incremented
before a push or call, the initial sp will be set to one byte
prior the
provided value. The provided value should not overlap
any other memory
areas such as used register banks or the data segment
and with enough space
for the current application.

d) I think there is a -o option now...


  • Johan Knol
    Johan Knol

    • status: open --> closed-fixed