Dear sdcc developers and users,
sdcc snapshot builds are succesfully build and uploaded to the
sourceforge file release area, but they are unfortunately not available
for download.
I added the support request to the existing one, describing the same
problem:
http://sourceforge.net/apps/trac
If this is so, there is no need to regenerate the files: we can just put
our copyright on the existing ones and declare that they are GPLed...
Borut
On 03/30/2011 08:31 PM, Weston Schmidt wrote:
> Preface: I'm not a layer.
>
> I read the copyright information sections in several of the
> datas
Dear sdcc developers and users,
the sdcc regression test results are from now on stored in a
database at sourceforge. Actually everything is stored in a single
table:
regtest_results
Table comments: regression test results
1 04:03 PM, Borut Ražem wrote:
Dear sdcc developers and users,
the sdcc regression test results are from now on stored in a
database at sourceforge. Actually everything is stored in a single
table:
regtest_results
Table comments: regre
st results
database
in CSV format:
- download the full database in compressed format (probably bzip2)
Borut
On 05/22/2011 06:14 PM, Borut Ražem wrote:
First step is already implemented: the regression test results
database can be downloaded fro
Dear fellows,
I think I discovered a bug in gcc 4.6 on Solaris i386. It appeared in
sdcc bitfields.c host regression test in svn build 6665, when -O2 gcc
option was included.
Here is the code in file t.c, which reproduces the bug:
8<
#include
#pragma GCC optimize ("O2")
const struct
{
Hi,
Dave McGuire sent me a mail that he is moving his network, including the
sdcc snapshot build servers, to his new facility. The servers will be
down for some time, probably a week or so.
This means that sdcc snapshot build will not be done for FreeBSD/x86,
NetBSD/i386, NetBSD/sparc64, OpenB
Hi,
Steven already replied me that there is a chance for the Mac OS X build
machine to be back this weekend.
Let hope for the best...
Borut
On 07/30/2011 10:40 AM, Borut Ražem wrote:
> Hi,
>
> Dave McGuire sent me a mail that he is moving his network, including
> the sdcc sn
And now the great news: Mac OS X snapshot build machine is back!
Zillion thanks to Steven!
Borut
On 07/30/2011 11:26 AM, Borut Ražem wrote:
> Hi,
>
> Steven already replied me that there is a chance for the Mac OS X
> build machine to be back this weekend.
> Let hope for the be
A lot of offers, these days!
I'm thinking about moving the DCF server to an other machine which
fulfills the flowing criteria as much as possible:
- it has a lot of network bandwidth, since it is acting as a mediator
between snapshot build machines and sourceforge File Release System: it
accept
quot;, but I'm not, so I never wrote
that! ;-)
P.S. for Windows users: don't even try to take this as an offence: I'm
just in mood to play with words. I'm still using Windows at my job, so
I'm joking on my account too.
Borut
On 07/31/2011 05:28 PM, Dave McGuire wrote:
%
Borut
On 07/31/2011 09:18 PM, Philipp Klaus Krause wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 31.07.2011 19:29, schrieb Borut Ražem:
>> The fact is that the big majority of sdcc users is running Windows:
>> see snapshot builds download statis
On 07/31/2011 10:19 PM, Philipp Klaus Krause wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 31.07.2011 21:56, schrieb Borut Ražem:
>> Philipp, you are definitely right: the numbers are not accurate, but
>> they already include source tarballs. No
On 08/03/2011 07:02 AM, Xiaofan Chen wrote:
> You should write "majority of the Windows users". There
> are quite a few Windows users who can build sdcc using
> Cygwin or MinGW/MSys. After all, sdcc is not that difficult
> to be built, not like gpsim.
>
> I can only guess that there are less than 1
I moved the sdcc development documentation from svn doc directory to
sdcc wiki, since the documentation is obsolete / unmantained / not valid
and it is not meant for sdcc users but for sdcc developers. The only 2
documents remained there: srccman.lyx and TININative.txt. I'm not sure
about TININ
Hello sdcc users and developers,
from now on all x86 builds: Linux on i386 (i386-unknown-linux2.5),
Windows package with installer (i586-mingw32msvc-setup) and Windows 95,
98, ME, NT, 2000, XP, Vista or Windows 7 (i586-mingw32msvc) will be done
on a new sdcc DCF build machine named derna.
Wi
Hi sdcc users and developers,
if you carefully looked to the SDCC Snapshot Build web page, you might
noticed two new items: "Windows 64bit (experimental)
(x86_64-w64-mingw32)" and "Windows 64bit package with installer
(experimental) (x86_64-w64-mingw32-setup)".
Both contains the native 64 bi
All remaining TODO issues regarding the 64 bit Windows build and
packaging are (or at least should be ;-) now solved.
Anybody tried it?
Borut
On 09/01/2011 07:33 PM, Borut Ražem wrote:
Hi sdcc users and developers,
if you carefully looked to the SDCC Snapshot Build web page, you might
erial
> communication between a PC and an mcs51. I programmed an NXP P89V51RD2BN
> with the hex file, and the program worked as expected.
>
> So far the 64 bit version works fine and I'll continue to use it.
>
> Thanks, Rich.
>
>
>
> F
On 09/13/2011 03:09 PM, Rich Bayless wrote:
>> Now what makes me puzzled is the
>> precedence: if I
>> remember well the installer adds the new path at the
>> beginning (on the
>> left side) of the PATH variable, so in this case should be
>>
>> ...;c:\program files\SDCC;c:\program files (x86)\SDCC;
Dear sdcc developers and users,
I'm glad to announce a new sdcc developer: Leland Morrison.
He has done most of the work in the Rabbit 2000 port: the target code
generator, sdasrab assembler and ucsim support.
Everybody: say hello to Leland!
Thanks to Philipp and Leland sdcc now supports two n
Dear sdcc users and developers,
in order to unify the sdcc toolchain utility prefixes to "sd*" I propose
to rename "asranlib" to "sdranlib".
I don't have an idea how many of you are using "ar" format libraries
with the "asranlib" utility and what would such a (cosmetic) change mean
for you (up
Dear sdcc users,
I'm pleased to announce that the SDCC 3.1.0 is planed to be released on
2011-11-26.
*SDCC 3.1.0 release is dedicated to memory of Dennis M. Ritchie, father
of the C programming language.*
More info at
https://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.1.0%20Release
Bor
On 10/22/2011 11:25 PM, Butuza Tamas wrote:
>
> Ps: I realized that there is also a severe bug in gputils with this
> class of pic devices.
> At the moment it is impossible to create even a trivially simple
> program to these pics.
> Ps2:
> However I'm trying to figure out some workaround.
> Mayb
On 10/23/2011 08:21 PM, Butuza Tamas wrote:
> Dear Borut Razem,
> Thank you for the fast work.
> Hopefully it fix the problem.
> I tried to build gputils by myself but I had no success.
> I tried it on Ubuntu 11.04.
> I checked out the trunk from sourceforge svn, next downloaded the
> Byacc and fl
Hi Tamas,
in the mean time I released gputils 0.14.0 RC2. Widows 32bit setup
package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.0/gputils-0.14.0_RC2.exe.
Happy testing ;-)
And don't forget to let me know about results...
Borut
> On 10/24/2011 01:14 PM, Butuza Tama
I haven't received any complain, so I'm going to rename "asranlib" to
"sdranlib".
Borut
On 10/15/2011 05:48 PM, Borut Ražem wrote:
> Dear sdcc users and developers,
>
> in order to unify the sdcc toolchain utility prefixes to "sd*" I
> pro
Dear gputils users,
gputils-0.14.0 has been released. The source code package is available
at
http://sourceforge.net/projects/gputils/files/gputils/0.14.0/gputils-0.14.0.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.0/gputils-0.13.0.
Dear sdcc developers,
are we ready for the sdcc 3.1.0 RC1 planned for tomorrow?
Borut
On 10/16/2011 09:15 AM, Borut Ražem wrote:
Dear sdcc users,
I'm pleased to announce that the SDCC 3.1.0 is planed to be released
on 2011-11-26.
*SDCC 3.1.0 release is dedicated to memory of Den
On 11/04/2011 11:14 PM, Maarten Brock wrote:
>> Dear sdcc developers,
> Are you asking the developers through the user list?
>
Oops, sorry. But most of (or maybe all) sdcc developers are also sdcc
users, so no big harm was done, except spamming the sdcc-user list.
>> are we ready for the sdcc 3.1
I'm willing to add support for all missing pic14 enh. devices to gputils
and make a new release 0.14.1. If somebory wants to help me preparing
the gputils gpprocessors.c file, he is welcome!
It would be nice if this would be done before the sdcc RC2 release,
planned for nest weekend, so that we
SDCC 3.1.0 Release Candidate 1 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available at:
http://sourceforge.net/projects/sdcc/files/snapshot_builds/sdcc-3.1.0-rc1
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.so
Hi Raphael,
all enhanced 14 bit devices should be now supported by gputils svn head
(thanks to Gál Zsolt). I also fixed a nasty bug which made the gputils
0.14.0 unusable :-( . I'm still waiting for reports from Gál and Robert
Pearce about the stability. If everything is OK, I'll probably made
Hello Raphael,
On 11/11/2011 08:07 AM, Raphael Neider wrote:
> 1. I can check in only the new files using the old naming scheme
> (underscore) for consistency.
>
> 2. I can check in the new files using the old naming scheme plus
> updated versions of existing header files that have seen changes in
On 11/11/2011 02:46 PM, Butuza Tamas wrote:
> Dear sdcc developers,
>
> I cannot buid sdcc and gputils from source, therefore I could use precompiled
> binaries for testing.
Which platform (operating system) are you using? I'll prepare the
gputils from the svn head for you.
> These are a bit ol
Hi Tamas,
thanks for the report.
Linear ram is supported by gputils, although not profoundly tested.
Gputils 0.14.0 has serious bugs in this area, but in svn HEAD and in
0.14.1 ALPHA1 build the bugs should be fixed.
Linear ram is not supported by sdcc. I agree with you that it would be
nice t
SDCC 3.1.0 Release Candidate 2 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available at:
http://sourceforge.net/projects/sdcc/files/snapshot_builds/sdcc-3.1.0-rc2
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.so
SDCC 3.1.0 Release Candidate 3 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available at:
http://sourceforge.net/projects/sdcc/files/snapshot_builds/sdcc-3.1.0-rc3
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.so
Dear sdcc users and developers,
the sdcc 3.1.0 release packages are prepared and uploaded to the SF File
Release system https://sourceforge.net/projects/sdcc/files/. Packages
are the same as for sdcc 3.1.0 RC3: I just renamed them.
Please download, install and test them on different platforms a
A new release of SDCC, the portable optimizing compiler for 8051, DS390,
Z80, Z180, Rabbit 2000, HC08 and PIC microprocessors is now available
(http://sdcc.sourceforge.net).
Sources, documentation and binaries compiled for x86 Linux, x86 MS
Windows and PPC Mac OS X are available.
SDCC 3.1.0 Fea
Jamie and Maatren,
thanks for the reports.
Borut
On 11/27/2011 11:10 PM, Maarten Brock wrote:
> I had already installed RC3 on XP and found no problems.
> My apologies for not reporting it before. I also tested
> on Win98 without problems, after the fix in RC2.
>
> Maarten
On 11/27/2011 09:53 P
Michal,
see sdccman, chapters 3.1.4 - 3.1.6. I recommend to use ar formatted
libraries as described in chapter 3.1.6, since the sdcclib utility and
sdcclib formatted libraries might be obsoleted in the future.
Borut
On 12/06/2011 02:57 PM, Michal Hucik - ORDOZ wrote:
Hello,
I would like
Rich,
thanks for the report.
Borut
On 12/11/2011 04:30 PM, Rich Bayless wrote:
> Hello Borut,
>
> I downloaded the 32 bit windows setup from sourceforge by clicking on the
> green box that says 'Download setup-3.1.0.exe' and ran the installer.
>
> This PC is running 32 bit Windows XP, SP3.
>
Dear sdcc users and developers,
I've made some changes in sdcc preprocessor sdcpp, which depend on the
machine endianness. I'm not sure if the endianness detection works
correctly on i386 Mac OS X. Can somebody please try it on svn head or on
snapshot build equal or later then
sdcc-snapshot-u
Dear gputils users,
gputils-0.14.1 has been released. The source code package is available
at
http://sourceforge.net/projects/gputils/files/gputils/0.14.1/gputils-0.14.1.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.1/gputils-0.14.1.
Hello sdcc users and developers,
we have a new sdcc DCF Mac OS X i386 build machine named dhcp101. It
produces Mac OS X 10.4 i386/ppc universal binaries
(i386_universal-apple-macosx) which can be used on both i386 and ppc Mac
OS X architectures, same as the mirror-dorrs ppc machine does
(univ
On 19. 01. 2012 16:50, Butuza Tamas wrote:
> Dear SDCC developers,
>
> I found a bug when I tried to compile a code for pic16F1938. (14 bit enhanced
> core)
>
> The problem is: The optimizer breaks the code. Makes part of the code
> unreachable.
> Error message is:
> test.c:51: warning 110: condi
Hi Tamas,
problem is that sdcc puts all variables, including both arrays, in the
same section. The linker tries to allocate a continuous memory block for
the complete section, which is 125 bytes, and fails. Solution would be
to put each variable in it's own section, the same as the code
genera
The following works for me:
$ sdcc -mpic16 -p18F25J50 -E -Wp,-dM t.c
#define STACK_MODEL_SMALL 1
#define __pic16 1
#define __STDC_HOSTED__ 0
#define pic18f25j50 1
#define SDCC 312
#define SDCC_REVISION 7243
#define __18f25j50 1
#define SDCC_pic16 1
#define __STDC__ 1
So you should use #ifdef __18
Vaclav,
can you please add a feature request to both sdcc and gputils fearture
request trackers?
Borut
On 21. 02. 2012 21:31, Raphael Neider wrote:
> Dear Vaclav,
>
>> For one project I started to use PIC16F721. I haven't noticed that it is
>> still not yet supported.
> The PI16F72[01] parts
On 21. 02. 2012 21:31, Raphael Neider wrote:
> Dear Vaclav,
>
>> For one project I started to use PIC16F721. I haven't noticed that it is
>> still not yet supported.
> So the first will be to get support into
> gputils (maybe Borut can help here?
Done. PIC16{L}F72[01] are supported in gputils svn
On 25. 02. 2012 12:03, Raphael Neider wrote:
> Hi,
>
For one project I started to use PIC16F721. I haven't noticed that it is
still not yet supported.
>>> So the first will be to get support into
>>> gputils (maybe Borut can help here?
>> Done. PIC16{L}F72[01] are supported in gputils sv
On 25. 02. 2012 14:22, Raphael Neider wrote:
>>> SDCC supports the new devices since r7353.
> Oh, by the way, all build machines (and interested users) now require
> gputils r668+ to build successfully ... I'd guess that's probably OK
> for a non-release version of sdcc.
gputils is now updated to
I created a gputils Win32 snaphot build from svn revision 674 (current
head). You can find it at
http://sourceforge.net/projects/gputils/files/gputils-win32-snapshots/gputils-0.14.1-20120229-674.exe.
Borut
On 28. 02. 2012 07:58, KHMan wrote:
> On 2/28/2012 2:30 PM, Raphael Neider wrote:
>>> do
Hi,
I moved some old & obsolete files laying without links on sdcc web
folder to the sdcc wiki under "Obsolete documents" chapter:
* Home Made Single Sided PC BOARDS
* Building SDCC on NT4: A proposal
* Cygwin Help
* Flat Mode
* SDCC Tarballs and Binaries
Borut
-
Philipp,
can you give me some instructions how to create / install the hurd VM, so I
don't have to reinvent the wheel?
Would it make sense to create a hurd snapshot build VM?
Borut
On Sat, May 5, 2012 at 3:54 PM, Philipp Klaus Krause wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
Just guessing: did you re-run configure?
Borut
On Sun, May 20, 2012 at 12:58 AM, roelof 't Hooft wrote:
> Hi,
>
> I've downloaded the latest sdcc source and it fails
> to compile with the following error :
>
> ..
> SDCCmain.c:326: error: ‘r3ka_port’ undeclared here (not in a function)
> make
In p18f45j50.inc from gputils and from mpasm is written:
; IMPORTANT: For the PIC18 devices, the __CONFIG directive has been
; superseded by the CONFIG directive. The following settings
; are available for this device.
This is why there are no __config definitions in
On 25. 05. 2012 18:43, Richard Hughes wrote:
> I've built master, and tried that. On initial try it worked fine, but
> trying to build my firmware image I'm getting:
>
> test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored
>
> It seems sdcc expects:
>
> #pragma config WDTEN=ON
>
>
>
> #pragma configure CP0=OFF,OSCS=ON
>
> The former is the correct one, isn't it?
>
> Thanks
>
>
> On Fri, May 25, 2012 at 9:27 PM, Borut Ražem wrote:
>
>> On 25. 05. 2012 18:43, Richard Hughes wrote:
>> > I've built master, and tried that. O
"allow space characters in #pragma config" problem fixed in svn revision
#7792.
Borut
On 26. 05. 2012 10:58, Diego Herranz wrote:
Thanks!
On Sat, May 26, 2012 at 10:37 AM, Borut Ražem <mailto:borut.ra...@gmail.com>> wrote:
#pragma config is correct. #pragma configu
= HSPLL_HS
>> [...]
>>
>> Warnings:
>> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s);
>> pragma ignored
>> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s);
>> pragma ignored
>>
>> Maybe a problem
#pragma config accepts underscore characters in svn revision #7797.
Borut
On Sun, May 27, 2012 at 11:51 PM, Diego Herranz <
diegoherr...@diegoherranz.com> wrote:
> Great! Thank you.
>
> On Sun, May 27, 2012 at 10:47 PM, Borut Ražem wrote:
>
>> Yes, the problem are unde
Dear gputils users,
gputils-0.14.2 Release Candidate 1 is available at
http://sourceforge.net/projects/gputils/files/gputils/0.14.2/gputils-0.14.2_RC1.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.2/gputils-0.14.2_RC1.exe.
Final rele
Dear gputils users,
gputils-0.14.2 Release Candidate 1 is available at
http://sourceforge.net/projects/gputils/files/gputils/0.14.2/gputils-0.14.2_RC1.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.2/gputils-0.14.2_RC1.exe.
Final rele
Dear gputils users,
due to the fix of bug # 3526915 - "Wrong crossreferences in the COD
file." and some other small fixes (see the ChangeLog) I decided to make
an other gputils release candidate: RC2.
Gputils-0.14.2 Release Candidate 2 is available at
http://sourceforge.net/projects/gputils/
SDCC 3.2.0 Release Candidate 1 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available at:
http://sourceforge.net/projects/sdcc/files/snapshot_builds/sdcc-3.2.0-rc1
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.so
Tamas,
try to use "#pragma config" to define configuration bits (see sdccman). You
should use a recent sdcc version which implements it. I suggest to use sdcc
3.2.0 RC1, so it will be additionally tested.
Let us know if it works for you. If it works, then we should remove config
words definitions
Dear gputils users,
due to the application of patch #3536090 - "This is the patch fixes some
INC files." I decided to make the third gputils release candidate: RC3.
Gputils-0.14.2 Release Candidate 3 is available at
http://sourceforge.net/projects/gputils/files/gputils/0.14.2/gputils-0.14.2_RC3
On Fri, Jun 22, 2012 at 5:56 PM, Gál Zsolt wrote:
> Hello,
>
> I realised that my programs doesn't work if I don't use a simple
> routine to avoid linking the sdcc_gsinit_startup code. It could be
> problematic for those sdcc users who started to use sdcc for a couple
> months ago. I am using thi
I have an impression that __code acts oposite as intendend: if __code is
defined, then _cinit is assumed to be in data memory - see the generated
asm with BANKSELs, which is wrong.
Omitting "__code" in line 71 is just a (ugly) workaround since "__code
cinit_t *cptr" seems to be correct: cptr IS a
ut program memory isn't changeable.
>
The cinit_t structure members are read from the program memory, they are
never written. I still think that __code qualifier is ok.
Borut
> 2012/6/23 Borut Ražem :
> > I have an impression that __code acts oposite as intendend: if __code is
>
Raphael,
thanks, I knew who I have to ask for help ;-)
There were many changes since the RC1 release, so I plan to make the RC2
release earlier: 2012-06-24 and make the RC3 at the date RC2 was originally
planned: 2012-07-01.
I will apply Raphael's patch immediately since the currently generated
SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available in
corresponding folders at:
http://sourceforge.net/projects/sdcc/files
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.source
Dear gputils users,
gputils-0.14.2 has been released. The source code package is available
at
http://sourceforge.net/projects/gputils/files/gputils/0.14.2/gputils-0.14.2.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.2/gputils-0.14.2.
SDCC 3.2.0 Release Candidate 3 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available in
corresponding folders at:
http://sourceforge.net/projects/sdcc/files
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.source
Diego,
thanks for the report.
Borut
On 29. 06. 2012 20:01, Diego Herranz wrote:
PIC16 (18F4550) tested on linux x86. Exactly the same code generated
than RC2.
Regards,
Diego
On Fri, Jun 29, 2012 at 6:56 PM, Borut Ražem <mailto:borut.ra...@gmail.com>> wrote:
SDCC 3.2.
On 30. 06. 2012 16:49, Claude Sylvain wrote:
> On 2012-06-24 14:54, Borut RaÂem wrote:
>
>> SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86
>> Linux, 32 bit Windows and universal Mac OS X are available in
>> corresponding folders at:
>> http://sourceforge.net/projects/sdcc/
On Sat, Jun 30, 2012 at 9:28 PM, Claude Sylvain <
csylv...@electro-technica.com> wrote:
>
> On 2012-06-30 14:37, Borut Ražem wrote:
>
> >
> > On 30. 06. 2012 16:49, Claude Sylvain wrote:
> >
> >> On 2012-06-24 14:54, Borut RaÂem wrote:
> >>
ceforge.net/projects/sdcc/files/sdcc-win32/3.2.0/sdcc-3.2.0-rc3a-setup.exe/download.
P.S.: the Windows setup package content is exactly the same as for RC3.
This change does not affect packages for other platforms.
Borut
On 29. 06. 2012 18:56, Borut Ražem wrote:
> SDCC 3.2.0 Release Candidate 3
On Sun, Jul 1, 2012 at 10:05 PM, Philipp Klaus Krause wrote:
> On 01.07.2012 16:12, Michael Hawkins wrote:
> > Can
> > anyone point me a general direction to begin?
>
> Look at the structure of the existing ports: Is the 8085 similar enough
> to one so th eports can share a lot of code (hc08 and
SDCC 3.2.0 Release Candidate 4 source, doc and binary packages for x86
Linux, 32 bit Windows and universal Mac OS X are available in
corresponding folders at:
http://sourceforge.net/projects/sdcc/files
If you find a mistake, please send a mail to sdcc-devel mailing list
sdcc-de...@lists.source
Dear sdcc users and developers,
the sdcc 3.2.0 release packages are prepared and uploaded to the SF File
Release system https://sourceforge.net/projects/sdcc/files/. Packages
are the same as for sdcc 3.2.0 RC4: I just renamed them.
Please download, install and test them on different platforms a
Dear sdcc users and developers,
the sdcc 3.1.0 release packages are prepared and uploaded to the SF File
Release system https://sourceforge.net/projects/sdcc/files/. Packages
are the same as for sdcc 3.1.0 RC3: I just renamed them.
Please download, install and test them on different platforms a
Probably you already guessed that I meant sdcc 3.2.0 release packages
which are just renamed 3.2.0 RC4 packages.
Borut
On 09. 07. 2012 09:26, Borut Ražem wrote:
> Dear sdcc users and developers,
>
> the sdcc 3.1.0 release packages are prepared and uploaded to the SF
> File Release
A new release of SDCC, the portable optimizing compiler suite for Intel
MCS51 based (8031, 8032, 8051, 8052, etc.), Maxim (formerly Dallas)
DS80C390 variants, Freescale (formerly Motorola) HC08 based (hc08, s08),
Zilog Z80 based (z80, z180, gbz80, Rabbit 2000/3000, Rabbit 3000A) and
Microchip P
improvements in the z80, hc08 and r2k code generation,
reducing code size.
* Shift, multiplication, division and returning of long long are now
supported (modulo for long long is still missing, integer literals of
type long long are broken).
Sorry,
Borut
On 09. 07. 2012 19:20, Borut Ražem wrote
On Wed, Aug 1, 2012 at 8:46 AM, Kustaa Nyholm wrote:
> Hi,
>
Hi Kusti,
> a fried is using a piece of code I wrote and is getting a bunch of these
> warnings which I'm not seeing:
>
> main.asm:19:Warning[212] __CONFIG has been deprecated for PIC18 devices.
> Use directive CONFIG.
>
This warning
Dear sdcc users and developers,
some of you probably already noted that we have a new snapshot build:
Rasbian on ARMv6 armhf (armv6l-unknown-linux-gnueabihf). The news is
that today the regression test star changed it's color from red to
green, which means that all regression tests pass (see
Hi Tijl,
I think we already had a similar problem on spark platforms. That's why
there is sparc.h file in include/opcode directory. I already added
ia64.h in svn revision #8144. Can you please try it and report the result?
Please fill the bug report anyway so that this change will remain
doc
Dear gputils users,
gputils-0.14.3 has been released. The source code package is available
at
http://sourceforge.net/projects/gputils/files/gputils/0.14.3/gputils-0.14.3.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.14.3/gputils-0.14.3.
Dear gputils users,
gputils-0.15.0 has been released. The source code package is available
at
http://sourceforge.net/projects/gputils/files/gputils/0.15.0/gputils-0.15.0.tar.gz.
Widows 32bit setup package is at
http://sourceforge.net/projects/gputils/files/gputils-win32/0.15.0/gputils-0.15.0.
In your case delay.c is compiled for the default mcs51 target, since you
didn't specify -m and -p sdcc command line option.
Try with *sdcc -V ***-mpic16 -p18f4550* -c delay.c*.
Borut
On 30. 11. 2012 22:24, Caio Rodrigues wrote:
Hello users of the SDCC list:
I am trying to create a pic18f4550
You are using wrong tool to create the pic library: you should use the
gplib librarian which is a part of gputils.
Borut
On 30. 11. 2012 23:40, Caio Rodrigues wrote:
Thanks Borut Ražem and Douglas Goodall for the advices.
I think sdcc compiles by default for the 8051 core and the sdcclib
Dear sdcc users and developers,
as you may already be aware, SourceForge is upgrading to a new platform
(code-named Allura), and as a result, the Classic SourceForge platform
will be retired. This also means that the Trac system will not be
available any more. The (old) sdcc wiki is a Trac wik
On 04. 12. 2012 23:22, Maarten Brock wrote:
> Hi,
>
> Is the user base coupled with SourceForge or should we
> all register at this wiki again?
You have to register to wiki again.
Borut
> Maarten
>
>> Dear sdcc users and developers,
>>
>> as you may already be aware, SourceForge is upgrading to
I have to configire mailing...
Borut
On 06. 12. 2012 11:10, Maarten Brock wrote:
> Hi,
>
> I just registered and it partially failed:
>
> SDCC wiki could not send your confirmation mail. Please
> check your e-mail address for invalid characters.
> Mailer returned: Unknown error in PHP's mail() fu
I propose to create separate branches in sdcc svn tree rather then open
new sf projects for such developments. I think that Philipp and Leland
already proved it with their work on rabbit port, optralloc ant other
sub projects.
Borut
On 06. 12. 2012 20:26, Vaclav Peroutka wrote:
Dear Daniel,
See http://sourceforge.net/p/forge/site-support/1896/.
Sdcc wiki was yesterday attacked by spammers so I disabled user
self-registration. Please contact me if you need the write access.
Borut
On 06. 12. 2012 13:30, Borut Ražem wrote:
I have to configire mailing...
Borut
On 06. 12. 2012
I'll take a look for anti-spam options.
> Please tell me if I'm totally wrong.
Only partially ;-)
Borut
> Maarten
>
>> See http://sourceforge.net/p/forge/site-support/1896/.
>>
>> Sdcc wiki was yesterday attacked by spammers so I disabled user
>> self-
1 - 100 of 121 matches
Mail list logo
