Hi Philipp,
Am 20.07.2016 um 19:57 schrieb Philipp Klaus Krause:
> [..]
> * Multiplication of 16-bit numbers by 7 or 100¹
> [..]
>
> ¹ this will later be generalized to other numbers that have few nonzero
> bits in canonical signed digit representation (RFE #505).
just a note, early PIC14 had ha
Hi,
eventually you could integrate into
https://www.flashrom.org/
Has a different focus but maybe it fits.
Greetings,
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Anal
Am 06.06.2015 um 09:50 schrieb Philipp Klaus Krause:
> On 05.06.2015 16:12, Simon Dible wrote:
>> Hi
>>
>> I'm working on an 8051 FPGA image that has broken logical operations on
>> the carry flag, at this time its not viable to fix them. Is there some
>> way to make sdcc for the 8051 not generat
Hello Georg,
Am 26.02.2015 um 19:02 schrieb Georg Icking-Konert:
>
> Does it work with STM8 for you? For a brief feedback thanks a lot in advance!
>
I only used with an STM32L151 so cannot speak for STM8.
The commit logs https://code.google.com/p/stm32flash/source/list
show no stm8 specific com
Hi Georg,
Am 17.02.2015 um 21:05 schrieb Georg Icking-Konert:
> - created Win, Linux, and MacOSX batch scripts to compile and upload via
> https://github.com/gicking/STM8_serial_flasher
thanks! Just want to note, that there is another project with
overlapping/similar functionality over here:
Hi,
Am 11.07.2014 10:48, schrieb Ben Shi:
> I built SDCC (with only the STM8 port enabled) and did regression test on an
> ARMv7 machine, and the build procedure cost 40 minutes, the only stm8
> regression test cost 3 hours.
>
> Is there anybody has ever tried the same work, and how to improve
Sorry, Maarten that I picked the wrong one. Unfortunately I do not have access
to the system until Monday. Someone else would have to step in?
Greetings,
Frieder
Maarten Brock schrieb:
>Hello Frieder,
>
>Thank you, but could you please retry with
>sdcc-3.3.0-rc4-x64-setup.exe from
>https://so
Hi Maarten,
Installation and compiling some small (mcs51) files with
sdcc-20130518-8610-x64-setup.exe (accepting all defaults)
went very smooth over here. (Win7 prof 64bit)
Thanks!
Frieder
--
AlienVault Unified Security
Hi Sirius,
Am 09.09.2012 06:56, schrieb Sirius:
> I found program even didn't went into main(). But if I delet pdata's 40 or
> make xram small than 250 it
> will work. It is so ridiculous!
sounds watchdog related.
The Silabs forums can occasionally be ridiculously slow (*) but eventually you
Hi again,
and on 2nd look you should also reduce "--xram-size 0x1000"
to 0x0f00 or the maximum xdata size your device has.
The smaller of the two values.
Greetings,
Frieder
--
Live Security Virtual Conference
Exclusive l
Hi Misha,
Am 17.06.2012 02:40, schrieb Misha Manulis:
> LDFLAGS = --stack-auto --code-loc 0x --code-size 0x8000 --xram-loc
> 0xf000 --xram-size 0x1000 --data-loc 0xff00 --xstack
"--data-loc 0xff00"
this one is out of range. Data/idata memory is within the first 256 byte.
The CC1110 a
Hi Raphael,
Am 20.04.2012 01:05, schrieb Raphael Neider:
> starting with svn 7610, sdcc/pic16 allows read/write access EEPROM via
> generic pointers in the range of 0x40_ to 0x7F_ (though only
Please add a compiler warning for write access (where possible).
It is _very_ easy to get the w
Am 09.07.2011 05:26, schrieb Charles Wilkins:
> After some further tinkering I was able to get SDCC generated instructions to
> work with EdSim51 by passing SDCC the following option:
> --iram-size 128
> I still am curious why, however, MOVX is in the disassembly.
> Charles
Hi Charles,
if you l
Hi Philipp,
Am 11.01.2011 23:29, schrieb Philipp Klaus Krause:
> Here's some data from a random application (which contains more data
> than code, so the real improvement in the generated code is much bigger
> than these numbers suggest):
>
> Old register allocator:
> 32768 bytes
>
> New registe
Hi Philipp,
Am 10.01.2011 21:55, schrieb Philipp Klaus Krause:
> Am 10.01.2011 20:57, schrieb Maarten Brock:
>> Philipp,
>
>> Why not just commit this to subversion? We are nowhere
>> near a release so this should not hurt too much. And you
>> even claim it passes all current regression tests.
Hi 谢继雷,
Am 14.07.2010 03:03, schrieb 谢继雷:
> When writing naked inline asm functions, how to declare those registers
> used by the function,
> without push/pop to stack?
Unfortunately SDCC does not support this, so unfortunately
there is nothing like callee-clobers-registers R4,R5 or
callee-saves-
Hi,
Am 11.04.2010 08:44, schrieb Dave McGuire:
> On 4/11/10 2:14 AM, Ori Idan wrote:
>> Does anyone knows where can I get 8051 core to be implemented on Altera
>> FPGA?
>
>Is there one on opencores.org? There are many processor cores there;
In addition to the 8051 cores at opencores there
Hi Sébastien,
Am 26.02.2010 10:02, schrieb Sébastien Lorquet:
> probably off topic, sorry, but what I miss in the 8051 port is a 16
> bit-stack pointer in xdata mode :(
Would swapping out contents of the 8051 hardware stack to
xdata memory help?
Appending untested sample code that tries to imple
Hi Jacques,
Jacques Pelletier schrieb:
> The crash was due to empty data record (length = 0 bytes). I´ve corrected the
> bug and made a new release of Hex2bin.
>
> Thanks!
Thanks and greetings,
Frieder
--
This SF.Net e
Hi,
Anthony Asterisk schrieb:
> I am using a commerical programmer called flashpro-cc. I will contact
> their support to find out if they can handle the unsorted/extended intel
> hex files.
While they should, there are also reasons why in some cases
you need sorted (address in strictly ascendin
Hi Caitlin,
caitilin lopez schrieb:
> I tried to submit a bug report and it said that I need to register. So I did.
>
>
> I did some more investigation about my issue (the compiler generates bad
> output). If I generate the assembly files then I use aslink in the assembly
> file the result i
Hi Gordon,
Gordon Henderson schrieb:
>> is there any command that parses the .hex files and tells you the how
>> much code ?
>
> Actually, I've just found out by accident that the standard unix 'size'
> command will parse the hex files - approximately. I guess it just lumps
> everything into on
Hi Gordon,
Gordon Henderson schrieb:
> void mathTest (uint16_t x)
> {
>uint32_t y ;
>uint32_t i = 0 ;
>
>for (;;)
>{
>
> y = (uint32_t)x * 9668 + 500 ;
> if (y != 4225416L)
> {
>serialPuts ("Curruption @ ") ;
> ...
> }
> ++i ;
>
>}
>
>
Hi Prateek,
(like Maarten I cannot see anything wrong with
your code or the generated assembly,)
just a guess, could you try:
unsigned char serial_read(){
unsigned char c;
while(!RI);
c = SBUF;
RI = 0;
return c;
}
instead of:
unsigned char serial_read(){
Hi Randy,
bob...@comcast.net schrieb:
> Instead of packihx, try:
>
> makebin -p test.bin
If you want more please use srecord http://srecord.sourceforge.net/
It's cross platform, free (beer and freedom) and a lot better than
*anything* that I've commercially seen.
For the immediate need to conve
Hi Gudjon,
Gudjon I. Gudjonsson schrieb:
> Hi
>The Debian package has been upgraded and a prerelease can be found on my
> server. Please test if you are interested.
thanks for the Debian packaging! I'm not (really) a Debian user
but nevertheless render SDCC being part of Debian _much_ more
i
Hi,
Joe G (Home) schrieb:
> I found an old document on the Infineon web site that show the differences
> beween Keil and SDCC. (Sept 2007).
>
> http://tinyurl.com/64h9z9
>
> I guess SDCC has improved sine the release date of this document.
>
> What additional features have been added to SDCC.?
Hi Matt,
Matt Baker schrieb:
> With sdcc -mz80 test.c I get
> at 1: error 131: cannot generate code for target 'z80'
>>> *"sdcc --version *reports
>>> SDCC : avr/pic16/pic14/xa51 2.8.0 #5117 (Jun 2 2008) (UNIX)
The SDCC you are using had been compiled for a subset of SDCC's
target CPUs. And Z80
Hi Andy,
Andy Green schrieb:
> The code for printf (printf_large.c) is as follows. My question is,
> should the space conditions be '>=' rather than just '>' ? (I did some
Yes, good catch! Could you file a bug report so this is automatically
seen on sdcc-devel?
(if it's too much hassle I'll fil
Hi Rod,
Rod Boyce schrieb:
> I am witting some code for an 8051 and seeing that is looks to be
> missing an optimisation anyway I have distilled th ecode to this fragment:
>
> void display_update( unsigned char tens, unsigned char ones );
>
>
> void my_func( unsigned char my_value )
> {
>
Hi,
Wenbing Ma schrieb:
> int main()
> {
> unsigned int a1,b1;
>
> b1=0x1234;
> a1=*(unsigned int*)(b1);
>
> return 0;
> }
> Use 'sdcc main.c' to compile. SDCC reports "error 127: non-pointer type
> cast to generic pointer from type 'unsigned-int' to type 'unsigned-int
> generic *' ". Is
Borut Razem schrieb:
> I and Maarten Brock had a discussion and agreed to enable the floating
> point support in printf_large() function included in libsdcc.lib
> library, which is a part of sdcc distribution, for large,
> large-stack-auto, small-xstack-auto, medium-xstack-auto and
> large-xsta
Hi,
Brandon Fosdick schrieb:
> sdcc is generating an awful lot of instructions just to set some pins.
Strictly speaking Keil uses 4 instructions
whereas SDCC uses only 3 instructions for:
P0DIR = 0x0;
while(1)
P0 = 0xFF;
Both compilers use 8 bytes of code memory and the
same number of c
Hi,
Kustaa Nyholm schrieb:
> void stepperSeekPosition(int stepperNo, uint32 seekPosition) {
...
> int16 stepperGetState(int stepperNo){
could you try
void stepperSeekPosition(unsigned char stepperNo, uint32 seekPosition) {
and
uint16 stepperGetState(unsigned char stepperNo){
not that it
Maarten Brock schrieb:
> Ok, make it a const function pointer then. And to get
> rid of the warning add a cast too:
>
> void (* const fp)(void) = (void (*)(void))0xFFF0;
> fp();
Or directly:
((void (*)(void))0xFFF0)();
Greetings,
Frieder
--
I do not see these errors here, your report is probably fixed with SDCC 2.8.1
#5155
http://sourceforge.net/tracker/index.php?func=detail&aid=1864577&group_id=599&atid=100599
Greetings,
Frieder
--
This SF.net email is sp
Hi,
Maarten Brock schrieb:
> I'm sorry, but I have to contradict this. At one time I
> did have the idea to implement it, but have never made
> it that far. The define _gptrget.c is not
> SDCC_MODEL_MEDIUM but has an extra D
> (DSDCC_MODEL_MEDIUM) (disabled). If I had implemented
> this I cer
Hi Mark,
Maarten Brock schrieb:
> The difference is that medium model puts the variables
> in pdata and large in xdata. Pdata (max. 256 bytes) is
> smaller than xdata (max. 64kB) but can be accessed with
> two pointers (r0,r1) what might result in smaller code
> than xdata which only can use d
Hi,
Dave McGuire schrieb:
> instructions. The 87C751 doesn't implement LCALL or LJMP (nor MOVX
> for that matter) because it has only 2KB of on-chip code memory and
> no external RAM capabilities. If memory serves, the offset width for
> ACALL and AJMP is 11 bits, which should be enough to
[EMAIL PROTECTED] schrieb:
> along those lines, has anyone been successful at running the Keil
> compiler .exe pieces under Wine? i did the experiment at one point,
> and got the compiler to run, but since i hadn't configured a license
> key (i didn't want to disturb my existing license, and i onl
Hi Richard,
Richard Erlacher schrieb:
> words, ... like NOT ... I won't have time for it either. I've been trying
> to figure out how to get anything useful out of SDCC, but the instructions
> for Windows (Yes, I'm one of those ...)tell you how to build it, but say
> nothing about how to use i
Hi
Richard Erlacher schrieb:
> I don't know how this happened, but my CA virus scanner turned up a virus
> (Win32FakeAV.CX) in SDCC-2.8.0-setup.exe. Forewarned is forearmed.
Checksums of sdcc-2.8.0-setup.exe as downloaded today from
http://sourceforge.net/project/showfiles.php?group_id=599&pack
Hi Maarten, hi Paul,
Maarten Brock schrieb:
> Hi,
>
> I've never used any but I wonder what a lint would do
> with this.
>
> Maarten
>
>
>> frieder wrote:
>> > Hi Arkadi
>> >
>> > Arkadi Shishlov schrieb:
>> > > Is it possible to get a warning from the compiler for suspicious lines
>> o
Hi Arkadi
Arkadi Shishlov schrieb:
> Is it possible to get a warning from the compiler for suspicious lines of
> code like
> some_var == 123;
> that makes little sense.
> ?
Indeed!)
This one probably makes even less sense but also
passes without error (both GCC and SDCC:)
--8<
Hi Richard,
Richard Erlacher schrieb:
>>> simulator, as the company that owns/owned it no longer exists.
>> Can you be more explicit? - which simulator?
>>
> TS Controls under the MIDE. There was a link in the SDCC context, so I
> loaded it up. It works very nicely, AFAIK, but ... it only works
Hi Richard,
Richard Erlacher schrieb:
> What is it that you fellows use to simulate 805x ASM code? I've found that
> the simulator bundled with SDCC for Windows doesn't operate on code that
> spans over 2 KB of memory, and I find I can't buy a "full" version of that
> simulator, as the company
Hi,
[EMAIL PROTECTED] schrieb:
> Internal RAM layout:
> 0 1 2 3 4 5 6 7 8 9 A B C D E F
> 0x00:|0|0|0|0|0|0|0|0|b|b|b|b|c|Q|Q|Q|
> 0x10:|Q|Q|Q|Q|Q|Q| | | | | | | | | | |
> 0x20:|B|T|a|a|a|a|a|a|a|a|a|a|a|a|a|a|
> 0x30:|a|a|a|a|a|a|a|a|a|a|a|a|a|a|a|a|
> 0x40:|a|a|a|a|a|a|S|S|S|S|S|S|S|S|S|S|
Hi,
[EMAIL PROTECTED] schrieb:
> [ beware -- list-crosspost ]
>
> it seems that at least some of the instability that i've been
> seeing is that the interrupt routines (and/or some of the
> routines they call) weren't reentrant, when i thought they would
Could the cause of this "instability" be
Hi Dani,
List schrieb:
> I'm not sure yet what I want :-)
:)
> The problem is that during the dma the on-chip xram does not need any
> special threatment, while the off-chip xram does.
Would it be correct to say: if you limit DMA to on-chip xram
then according to section 6.3 of:
http://www.
Hi
Sebastian N. Fischmeister schrieb:
>I'm looking for a couple of source code examples that can be
> compiled with SDCC. I need them for testing our static analysis
> methods for microcontroller programs.
You could use OpenEC, which is (the start of) an open source
implementation of the
Hi Martin,
Martin Leopold schrieb:
> inline. The code is generated by the precompiler nesC and introduces a
> very high number of superfluous function calls to be inlined by the
> compiler. I've attached a cutout from a larger program that fails with
> the following error:
>
> sdcc -mmcs51 --std-
Hi,
Martin Leopold schrieb:
> I'm trying to compile my port of TinyOS using SDCC*, but I'm running
> into some problems. One problem is the following: one program runs fine
> with the default memory mode (small i presume), but fails with the
> following error when switching to large:
>
> ...
> ?A
Hi Martin,
Martin Leopold schrieb:
> problems with sdcc. The statement returns a bunch of warnings and fails
> in the assembler with the following error:
>
> sdcc -mmcs51 test_condit.c
> test_condit.c:15: warning 94: comparison is always false due to limited
> range of data type
> test_condit.c
Hi Alan,
Alan Carvalho de Assis schrieb:
> Hi Mukund,
>
> 2007/11/7, Mukund Deshmukh <[EMAIL PROTECTED]>:
>> I have whole lot of code for ADC and soft serial port between _asm and
>> _endasm;
Mukund's mail seems to have arrived with a delay of 4 days on the list.
Is he the only one who suffers
Hi Eric,
Eric Jonas schrieb:
> Then I download to my device. When the buffer array size is < ~100
> bytes, or absent, the for loop in main runs and P0.1 toggles, which I
> can easily see on my scope.
not unlikely your problem is watchdog related:
http://www.cygnal.org/ubb/Forum10/HTML/76.html
Hi Mary-Ann,
Mary-Ann Johnson schrieb:
> The .asm files generated by the latest snapshot don't seem to list the
> peephole optimisations used, so I can't tell where peephole
> optimisations are being used any more.
use --fverbose-asm to get them again.
Greetings,
Frieder
---
Alan Carvalho de Assis schrieb:
> Hi David and Borut,
>
> 2007/11/6, David Lucena <[EMAIL PROTECTED]>:
>> Right, this is a preprocessor issue, not SDCC itself. No gnu cpp based
>> preprocesor preserves
>> newlines in the macros. But I am sure that SDCC accepts more than one
>> assembler line bet
Hi Peter,
Peter Kuhar schrieb:
> This is a follow up from the previous e-mails about code banking.
> I've posted the sdcc bankswitching code to
> http://sourceforge.net/projects/ccflasher/
> Patches and a sample app are included. Sample app works for cc2430,
Thanks! I downloaded and installed sdc
Hi,
Lee Russell schrieb:
> I apologise for the off topic nature of this post, but I have run out of
> other resources to ask the question of.
if it does not work out here you might also try asking on
http://www.8052.com/forum/ .
> I am, successfully, using SDCC on Linux, but my problems start w
Hi Tristan,
Tristan Willy schrieb:
> The Cypress EZ-USB FX2 chip needs to have _XPAGE defined to MPAGE (sfr @ 0x92)
thanks for sharing this. The problem you have solved is partly due to SDCC
not having a header file cy7c6801x.h within the distribution.
If there had been one you probably would no
Hi James,
James Tidman schrieb:
> Where, how, do I offer some improvements to the library code that comes
> with SDCC? I tinkered with the printf_tiny.c file and made some small
> improvements I would like to share.
did your improvements by chance add the capability to output
the formats %02x an
Hi Peter,
Peter Kuhar schrieb:
> hi,
>
> Has anyone allready implemented the bankswitching technichue described in
> http://sourceforge.net/forum/message.php?msg_id=3360254
>
> I'm currently adding a feature to the aslink to support that.
> Basicaly,
> The codesegments are configured at compile
Hi Gudjon,
thanks for providing the nice header file!)
It could go in "as is".
Yet I want to draw your attention to the latest
NXP/Philips header file distributed with SDCC:
http://svn.sourceforge.net/viewvc/sdcc/trunk/sdcc/device/include/mcs51/P89LPC925.h?view=markup
This most modern format
Hi europa989,
[EMAIL PROTECTED] schrieb:
> SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0
> #4309 (Jul 28 2006) (UNIX)
>
> using mac osx
thanks!
> oh, as for the apostrophe topic:
> the .c file is this:
>
> #include
>
> char str1[10];
>
> void main(vo
Hi,
Borut Razem schrieb:
> Which sdcc version are you using?
>
> sdcc --version
>
> Which OS (from the dir names I assume Mac OS X)?
>
> Can you try it with the latest snapshot build from
> http://sdcc.sourceforge.net/snap.php?
Guessing from the line numbers in the report:
/Users/name/test.c
There's a feature request for this:
http://sourceforge.net/tracker/index.php?func=detail&aid=882215&group_id=599&atid=350599
(a handy macro definition (handling 8 bit) is given there.)
It is probably consensus that as long as ANSI/ISO C does not
specify a notation for binary constants SDCC will h
Hi Arnab,
you have not reported back to the proposals Maarten or Sietse made.
a) If the proposals fixed your issue - fine.
b) If you wanted to get rid of the startup up code in order
to save some bytes code space then you won't feel helped.
So there's yet another (be warned: steeper) way to
d
Hi again,
and thanks for the quick update:)
Could you additionally change one of the occurrences of
"Silicon Labs" to "Silabs" and another one to
"Silicon Laboratories" to make it easier yet
for search machines?
One could also probably use the tool srecord
http://srecord.sf.net for some read/modi
Hello Rodolfo,
Rodolfo Giometti schrieb:
> I hope my message is not OT... :P
Not at all!!
You might want to also announce your tool on:
the "Development tools" section of Silabs forum:
http://www.cygnal.org/scripts/forumdisplay.cgi?action=topics&forum=Development+Tools&number=4&DaysPrune=45&Las
Hello Rodrigo,
Rodrigo Guerra schrieb:
> I am using an up-to-date Ubuntu Edgy (kernel 2.6.17-10) in an AMD64.
Probably not many SDCC developers have already switched
to 64 bit systems... So they might not be able to reproduce.
> The last error message I get looks like this:
> make[2]: Entering d
Hi,
"Maarten Brock" <[EMAIL PROTECTED]> schrieb am 25.12.2006 18:18:08:
> What you need is a properly typed copy of the pointer.
this one should work too:
gptr = ((unsigned char *) gptr) + 1;
Mr.Cashe, I'm not sure whether incrementing a parameter
passed to a function is what you want to do?
It
Hi Jan,
Jan Waclawek schrieb:
> Is this an error or just me being stupid?
It's a bug - please file a bug report about it.
The bug can be reproduced within the regression
test suite with the code below:
-8<-
/** bugxxx.c
*/
#include
#if de
Hallo,
Heiko Müller schrieb:
> we are using sdcc 2.4.0 (debian sarge) for uC ATMEL AT89C51ED2.
> The initialization of global xdata (XISEG) is not properly performed
> without option '-no-xinit-opt' when the internal XRAM of uC
> is used and XISEG ends above 0xFFh.
the AT89C51RD2/ED2 deviates f
Hi Felix,
Felix Brack schrieb:
> Here is the command line I use for sdcc:
>
> sdcc --model-large --xram-loc 0x0800 --code-loc 0x2000 --data-loc 0x30
> --idata-loc 0x30 -Wl -bBSEG=0x30 --iram-size 0x100 --no-pack-iram
> --debug ./build/stm.rel ...
sorry that this is unrelated to your
Hi Jon,
Jon Hallsten schrieb:
> Or does interaction with this buffer not require this protection?
If you need "more than byte-wise" access (for interpreting a command)
to the buffer you need some protection.
By handshake/protocol/timing/disabling_IRQ or whatever.
I would not recommend this.
Inst
Hi Maarten,
Maarten Brock schrieb:
> 5) There are no near term improvements to be expected on
> the use or location of temporaries.
there might be a way around this:
If there was a #pragma to control the segmentname
of the data locations on a per-function basis then
the user could do a overlayin
Hi Christer,
Christer Weinigel schrieb:
> I'm hereby releasing this file under a X11/MIT license and hope that
> you'll find it useful. Maybe you might even wanto to add it the main
> SDCC distribution. Also, please tell me if I have made any mistakes
> while writing this file, it's pretty easy
daniel ranc schrieb:
> On the page http://simplepic.atspace.com you'll find a "poorman's
> printf" in source code that you could adapt for your needs (without
> varargs).
Hi Daniel,
some remarks:
- an include file seems missing (INTBUFSIZE, uns8),
- putchar should (could) be in a separate file
Richard Erlacher schrieb:
> Gee! That seems to work quite well!
>
> Unfortunately, though I've now managed to open the source files, there's not
> a clue as to which files might give a little guidance as to how the
> assembler and the simulator are supposed to be used and how, exactly, they
>
Brandon Fosdick schrieb:
> Frieder Ferlemann wrote:
>> Here (recent SDCC on Opensuse 10.0) SDCC opens several temporary
>> files in the directory /usr/tmp (instead of /tmp or /var/tmp).
>
> Good call. It looks like sdcc is trying to use /usr/tmp on FreeBSD as well.
> I&#x
Hi Brandon,
Brandon Fosdick schrieb:
> [EMAIL PROTECTED] wrote:
>> Since 2.5.0 the ChangeLog has grown by more than 3000 lines so all
>> changes are simply too numerous to name.
>
> Is there a link to the changelog somewhere?
> I'm not seeing it on the website, but maybe I'm blind.
There's a lin
Hi Brandon,
Brandon Fosdick schrieb:
> I installed SDCC on my FreeBSD 6.1 box using land/sdcc
> also tried lang/sdcc-devel) and then tried to compile a
> small test file. But it's complaining about creating a
> temporary file. /tmp is world writeable so I'm not sure
> what the problem is. Any sug
Hi
Jatin Bhateja schrieb:
> I am working on SDCC for quite some time now. I have noticed that many a
> times iCode generation phase
Please repost on the developer mailing list. Your mail might go unnoticed here.
Greetings,
Frieder
Hi,
[EMAIL PROTECTED] schrieb:
> polling volatile variable TIMEOUT from main() is failed.
does it wait forever or
does it continue to soon or
does it continue irregularly?
> volatile unsigned int TICKS; // system ticks
> volatile unsigned char TIMEOUT; // system timeout flag
Hi,
Arvind Govindaraj (RBIN/EDU2) schrieb:
> I am currently working on SDCC. Can anybody please tell me where I can
> find documentation for the assembler included with SDCC?
there's a version online at:
http://svn.sourceforge.net/viewcvs.cgi/sdcc/trunk/sdcc/as/doc/asxhtm.html
(See also section
Richard Latter schrieb:
> using PCW a friend has managed to produce a .hex file of 175 bytes as
> opposed to the 820 generated by SDCC.
Comparing the size of Intel hex files is probably
not what you want, because it only gives an estimate
of the code size.
*If* the extra '.' in line 93 is removed
86 matches
Mail list logo
