From: Borut R. <bor...@si...> - 2010-10-10 15:15:38
|
Dear sdcc developers, please consider the svn main branch as frozen, which means that only fixes for high severity bugs (after an agreement on this mailing list) and changes in the documentation can be committed. The SDCC 3.0.0 release schedule is published at http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release Borut |
From: Borut R. <bor...@si...> - 2010-10-10 15:24:56
|
Please review the documentation. Raphael, please review / update the table of supported pic devices in sdccman.lyx Borut On 10/10/2010 05:15 PM, Borut Razem wrote: > Dear sdcc developers, > > please consider the svn main branch as frozen, which means that only > fixes for high severity bugs (after an agreement on this mailing list) > and changes in the documentation can be committed. > > The SDCC 3.0.0 release schedule is published at > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release > > > Borut > |
From: Borut R. <bor...@si...> - 2010-10-11 18:15:57
|
On 10/11/2010 06:12 PM, Sébastien Lorquet wrote: > Hi, > > No regression for me on winxp, using mplab and mplab-sdcc. Just had to > add the --use-non-free for PIC libraries. > Great! > about the doc: > is the pic port still considered "in development"? On my opinion it will be "in development" until it passes the regression tests. > the -mavr option is still documented. Is that port still included? > there is a right-aligned extra "!" at the end of page 39. and also at > the first paragraph of "tips" page 82 > at end of page 76 there is: on a single channel oscilloscope you could > f.e. > if that means "for example", then I think the proper abbreviation is > "e.g." > Fixed. Thanks, Borut > Thanks. > Sebastien > > On Sun, Oct 10, 2010 at 5:24 PM, Borut Razem <bor...@si... > <mailto:bor...@si...>> wrote: > > Please review the documentation. > > Raphael, please review / update the table of supported pic devices in > sdccman.lyx > > Borut > > > On 10/10/2010 05:15 PM, Borut Razem wrote: > > Dear sdcc developers, > > > > please consider the svn main branch as frozen, which means that only > > fixes for high severity bugs (after an agreement on this mailing > list) > > and changes in the documentation can be committed. > > > > The SDCC 3.0.0 release schedule is published at > > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release > > > > > > Borut > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating > great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > <mailto:sdc...@li...> > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2& L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Frieder F. <Fri...@we...> - 2010-10-11 22:11:36
|
Hi, > there is a right-aligned extra "!" at the end of page 39. and also at the first paragraph of "tips" page 82 They are there on purpose:) Maybe they some time will be some of those exclamation marks enclosed in a yellow triangle at the far left or right of a book. They were meant for info that could be easily overread and that could come as a surprise/trouble even for experienced users of other embedded compilers. Well, at least this is my notion of the extra '!'. Maybe not each ocurrence of this exclamation marks fits this criterion but they should _not_ be removed alltogether. (strictly speaking these exclamation marks are not right-aligned but are intended to be rendered right of the right margin (sorry if I didn't use the right terms). Note, these exclamation marks are not rendered in the html documentation, (which likely is a shortcoming of latex2html). But as html documentation presumably is not considered the primary source of information if pdf documentation is available this should be ignored for now?) Greetings, Frieder ___________________________________________________________ WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 |
From: Sébastien L. <sq...@gm...> - 2010-10-12 07:14:53
|
Hi, I understand now! But I do not think they are noticeable for what they are. A square box enclosing the important text might be easier to notice. I don't know if you can do that with latex, or if something else -- or the current situation -- is better. Sebastien On Tue, Oct 12, 2010 at 12:11 AM, Frieder Ferlemann < Fri...@we...> wrote: > Hi, > > > there is a right-aligned extra "!" at the end of page 39. and also at the > first paragraph of "tips" page 82 > > They are there on purpose:) Maybe they some time will be some of those > exclamation marks enclosed in a yellow triangle at the far left or right > of a book. > They were meant for info that could be easily overread and that could > come as a surprise/trouble even for experienced users of other > embedded compilers. Well, at least this is my notion of the extra '!'. > > Maybe not each ocurrence of this exclamation marks fits this criterion > but they should _not_ be removed alltogether. > > (strictly speaking these exclamation marks are not right-aligned but > are intended to be rendered right of the right margin (sorry if I > didn't use the right terms). > > Note, these exclamation marks are not rendered in the html documentation, > (which likely is a shortcoming of latex2html). > But as html documentation presumably is not considered the primary > source of information if pdf documentation is available this should be > ignored for now?) > > Greetings, > Frieder > ___________________________________________________________ > WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit > gratis Notebook-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > |
From: Raphael N. <rn...@we...> - 2010-10-12 12:32:53
Attachments:
paths.patch
|
Dear sdcc developers, > please consider the svn main branch as frozen, which means that only > fixes for high severity bugs (after an agreement on this mailing list) > and changes in the documentation can be committed. The include paths to the pic14 headers is wrong: pic14 uses just "pic" is its include path suffix, but port->target (which is used in the current implementation) is "pic14". As a consequence, even using --use-non-free does not help SDCC to find the PIC headers. I attached a patch that specifically handles this case for the pic14 target -- which is not too beautiful, but introducing another helper like PORT.general.get_model seems to be too much of a change for now. A more pleasant side-effect of the special treatment in SDCCmain.c is that the additional include path generation in pic/main.c is superfluous once the correct path is setup in SDCCmain.c -- a true improvement maintainability-wise. Alternatively, one could rename the pic directories (src/pic, device/include/pic, device/lib/pic) to pic14 -- which also seems to be too much for now. Awaiting your approval (or commit). Best regards Raphael |
From: Borut R. <bor...@si...> - 2010-10-12 14:01:16
|
On 10/12/2010 02:32 PM, Raphael Neider wrote: > Dear sdcc developers, > >> please consider the svn main branch as frozen, which means that only >> fixes for high severity bugs (after an agreement on this mailing >> list) and changes in the documentation can be committed. > > The include paths to the pic14 headers is wrong: pic14 uses just "pic" > is its include path suffix, but port->target (which is used in the > current implementation) is "pic14". As a consequence, even using > --use-non-free does not help SDCC to find the PIC headers. Thanks to finding it out. > > I attached a patch that specifically handles this case for the pic14 > target -- which is not too beautiful, but introducing another helper > like PORT.general.get_model seems to be too much of a change for now. > A more pleasant side-effect of the special treatment in SDCCmain.c is > that the additional include path generation in pic/main.c is > superfluous once the correct path is setup in SDCCmain.c -- a true > improvement maintainability-wise. > I agree. I added a TODO comment. > Alternatively, one could rename the pic directories (src/pic, > device/include/pic, device/lib/pic) to pic14 -- which also seems to be > too much for now. > This is what I intent to do after the release. It is not a low risk task, since it also affects the build & packaging process. > > Awaiting your approval (or commit). > Approved and committed. Borut |
From: Maarten B. <sou...@ds...> - 2010-10-18 19:42:34
|
Hi Borut, Since the original release schedule has not been met, do you have an updated schedule? I also have updated the manual a bit. Can I still commit that? Greetings, Maarten > Dear sdcc developers, > > please consider the svn main branch as frozen, which means that only > fixes for high severity bugs (after an agreement on this mailing list) > and changes in the documentation can be committed. > > The SDCC 3.0.0 release schedule is published at > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release > > > Borut |
From: Borut R. <bor...@si...> - 2010-10-19 15:35:09
|
On 10/18/2010 09:42 PM, Maarten Brock wrote: > Hi Borut, > > Since the original release schedule has not been met, do > you have an updated schedule? > I plan to release the RC2 latest during the next weekend. It seems that the current version is stable and we don't have show-stoppers, so I can make the RC2 from the tomorrow snapshot build, which will include your documentation changes. > I also have updated the manual a bit. Can I still commit > that? > > Yes, please! Documentation updates are always welcome and since they involve lo (no) risk we can include them in the late stages before the release. > Greetings, > Maarten > > >> Dear sdcc developers, >> >> please consider the svn main branch as frozen, which means that only >> fixes for high severity bugs (after an agreement on this mailing list) >> and changes in the documentation can be committed. >> >> The SDCC 3.0.0 release schedule is published at >> http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release >> >> >> Borut >> |
From: Borut R. <bor...@si...> - 2009-03-15 09:51:42
|
SDCC 2.9.0 Release Candidate 2 source, doc and binary packages for x86 Linux, 32 bit Windows and universal Mac OS X are available at: http://sdcc.sourceforge.net/snap.php If you find a mistake, please send a mail to sdcc-devel mailing list sdc...@li.... I would appreciate any reports about a success or failure of running pre-compiled binary packages. Borut |
From: Borut R. <bor...@si...> - 2009-03-15 09:55:15
|
Dear sdcc developers, the sdcc RC2 is released. Thanks to anybody helped to bring it to the life. Please consider the svn main branch as DEEPLY FROZEN, which means NOTHING can be committed without the agreement between sdcc developers and release manager. The SDCC 2.9.0 release schedule is published at http://sdcc.sourceforge.net/release_wiki/index.php?page=SDCC+2.9.0+Release. Borut Borut Razem wrote: > SDCC 2.9.0 Release Candidate 2 source, doc and binary packages for x86 > Linux, 32 bit Windows and universal Mac OS X are available at: > http://sdcc.sourceforge.net/snap.php > > If you find a mistake, please send a mail to sdcc-devel mailing list > sdc...@li.... > > I would appreciate any reports about a success or failure of running > pre-compiled binary packages. > > Borut > > |
From: Maarten B. <sou...@ds...> - 2010-10-25 18:33:17
|
Borut, I've installed RC2 on both WinXP and Win98 and it just works. Maarten > SDCC 3.0.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.0.0-rc2 > > If you find a mistake, please send a mail to sdcc-devel mailing list > sdc...@li.... > > I would appreciate any reports about a success or failure of running > pre-compiled binary packages. > > Borut > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Borut R. <bor...@si...> - 2010-10-25 19:04:47
|
Maarten, thanks for the report. Has anybody tried it on i386 and ppc Mac OS X? I'll be absent from tomorrow, 2010-10-26 until 2010-10-31. I won't be able to react if something urgent pops out, so please don't wait for me. If everything goes well, I'll prepare the sdcc 3.0.0 final release on 2010-11-01. P.S.: Maarten, thanks to discover and correct all the typos I produced :-[ Borut On 10/25/2010 08:32 PM, Maarten Brock wrote: > Borut, > > I've installed RC2 on both WinXP and Win98 and it just > works. > > Maarten > > >> SDCC 3.0.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.0.0-rc2 >> >> If you find a mistake, please send a mail to sdcc-devel mailing list >> sdc...@li.... >> >> I would appreciate any reports about a success or failure of running >> pre-compiled binary packages. >> >> Borut >> |
From: Sébastien L. <sq...@gm...> - 2010-10-11 16:13:07
|
Hi, No regression for me on winxp, using mplab and mplab-sdcc. Just had to add the --use-non-free for PIC libraries. about the doc: is the pic port still considered "in development"? the -mavr option is still documented. Is that port still included? there is a right-aligned extra "!" at the end of page 39. and also at the first paragraph of "tips" page 82 at end of page 76 there is: on a single channel oscilloscope you could f.e. if that means "for example", then I think the proper abbreviation is "e.g." Thanks. Sebastien On Sun, Oct 10, 2010 at 5:24 PM, Borut Razem <bor...@si...> wrote: > Please review the documentation. > > Raphael, please review / update the table of supported pic devices in > sdccman.lyx > > Borut > > > On 10/10/2010 05:15 PM, Borut Razem wrote: > > Dear sdcc developers, > > > > please consider the svn main branch as frozen, which means that only > > fixes for high severity bugs (after an agreement on this mailing list) > > and changes in the documentation can be committed. > > > > The SDCC 3.0.0 release schedule is published at > > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release > > > > > > Borut > > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Maarten B. <sou...@ds...> - 2010-10-20 06:24:24
|
It's in. > On 10/18/2010 09:42 PM, Maarten Brock wrote: > > Hi Borut, > > > > Since the original release schedule has not been met, do > > you have an updated schedule? > > > > I plan to release the RC2 latest during the next weekend. It seems that > the current version is stable and we don't have show-stoppers, so I can > make the RC2 from the tomorrow snapshot build, which will include your > documentation changes. > > > I also have updated the manual a bit. Can I still commit > > that? > > > > > > Yes, please! Documentation updates are always welcome and since they > involve lo (no) risk we can include them in the late stages before the > release. > > > Greetings, > > Maarten > > > > > >> Dear sdcc developers, > >> > >> please consider the svn main branch as frozen, which means that only > >> fixes for high severity bugs (after an agreement on this mailing list) > >> and changes in the documentation can be committed. > >> > >> The SDCC 3.0.0 release schedule is published at > >> http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release > >> > >> > >> Borut > >> > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Patryk <pa...@wp...> - 2012-06-17 21:00:10
|
I'm unable to download it from SF - there are 6 files in summary, but page seems to be empty (no links to files). Checked on 2 machines (XP and 7) with IE8. Home / snapshot_builds / sdcc-3.2.0-rc1 Name Modified Size Status Parent folder Totals: 6 Items 31.3 MB ----- Original Message ----- From: "Borut Razem" <bor...@gm...> To: "Sdcc-User" <sdc...@li...>; "Sdcc-Devel" <sdc...@li...> Sent: Sunday, June 17, 2012 5:07 PM Subject: [sdcc-devel] SDCC 3.2.0 Release Candidate 1 > 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 > sdc...@li.... > > I would appreciate any reports about a success or failure of running > pre-compiled binary packages. > > Borut > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Patryk <pa...@wp...> - 2012-06-25 00:26:15
|
I was able to successfully install and run RC1/RC2 on Win98. I have tested some previous 8051 project and after some tweeks it compiled and worked. Here are 2 issues spotted, not present in SDCC 3.1.0: 1) this may be Win98 specific - slashes in paths have doubled: SDCC 3.1.0 D:\MM\SiLabs_IDE\ADuC\main.c:116: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG SDCC 3.2.0 D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: warning 110: conditional flow changed by optimizer: so said EVELYN the modified DOG SDCC 3.2.0 *.asm: D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: ERROR: No such file or directory 2) extern __sfr16 sdcc -c test.c: extern __sfr16 __at(0xCDCC) TMR2; void f(void) { TMR2 = 0; } test.asm:108: Error: <r> relocation error No such problem with 8bit __sfr, removing "extern" also helps. Regards, Patryk ----- Original Message ----- From: "Borut Razem" <bor...@gm...> To: "Sdcc-User" <sdc...@li...>; "Sdcc-Devel" <sdc...@li...> Sent: Sunday, June 24, 2012 8:54 PM Subject: [sdcc-devel] SDCC 3.2.0 Release Candidate 2 > 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 > sdc...@li.... > > I would appreciate any reports about a success or failure of running > pre-compiled binary packages. > > Borut > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Borut R. <bor...@gm...> - 2012-06-25 05:43:19
|
On 25. 06. 2012 02:26, Patryk wrote: > I was able to successfully install and run RC1/RC2 on Win98. I have tested > some previous 8051 project and after some tweeks it compiled and worked. > > Here are 2 issues spotted, not present in SDCC 3.1.0: > > 1) this may be Win98 specific - slashes in paths have doubled: > SDCC 3.1.0 > D:\MM\SiLabs_IDE\ADuC\main.c:116: warning 110: conditional flow changed by > optimizer: so said EVELYN the modified DOG > SDCC 3.2.0 > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: warning 110: conditional flow changed > by optimizer: so said EVELYN the modified DOG > SDCC 3.2.0 *.asm: > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: ERROR: No such file or directory Patryc, can you please provide a short c source file which reproduce the problem? Can you please add the -V sdcc command line option, run compilation and send the result? Specially the "No such file or directory" error makes me nervous: it seems that it didn't happen in 3.1.0. I propose to open a bug report and supply / attach all the needed info there. > 2) extern __sfr16 > sdcc -c test.c: > extern __sfr16 __at(0xCDCC) TMR2; > void f(void) > { > TMR2 = 0; > } > test.asm:108: Error: <r> relocation error > > No such problem with 8bit __sfr, removing "extern" also helps. Maarten, will you take a look? > Regards, > Patryk Thanks for the precious report, Borut |
From: Maarten B. <sou...@ds...> - 2012-06-25 09:17:03
|
Hi, > On 25. 06. 2012 02:26, Patryk wrote: > > I was able to successfully install and run RC1/RC2 on Win98. I have tested > > some previous 8051 project and after some tweeks it compiled and worked. > > > > Here are 2 issues spotted, not present in SDCC 3.1.0: > > > > 1) this may be Win98 specific - slashes in paths have doubled: > > SDCC 3.1.0 > > D:\MM\SiLabs_IDE\ADuC\main.c:116: warning 110: conditional flow changed by > > optimizer: so said EVELYN the modified DOG > > SDCC 3.2.0 > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: warning 110: conditional flow changed > > by optimizer: so said EVELYN the modified DOG > > SDCC 3.2.0 *.asm: > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: ERROR: No such file or directory > > Patryc, can you please provide a short c source file which reproduce the > problem? Can you please add the -V sdcc command line option, run > compilation and send the result? Specially the "No such file or > directory" error makes me nervous: it seems that it didn't happen in 3.1.0. > > I propose to open a bug report and supply / attach all the needed info > there. I also noticed the double backslashes when SDCC generates an error: Source\\cmdintf.c:38: syntax error: token -> ';' ; column 20 But I don't know where the "No such file ..." comes from. I don't get that. > > 2) extern __sfr16 > > sdcc -c test.c: > > extern __sfr16 __at(0xCDCC) TMR2; > > void f(void) > > { > > TMR2 = 0; > > } > > test.asm:108: Error: <r> relocation error > > > > No such problem with 8bit __sfr, removing "extern" also helps. > > Maarten, will you take a look? I'll take a look into this. > > Regards, > > Patryk > > Thanks for the precious report, > Borut My projects compile clean now with RC2. Size is slightly different (some larger, some smaller). But BSEG symbols are missing from the .map file. Maarten |
From: Borut R. <bor...@gm...> - 2012-06-25 09:47:25
|
On Mon, Jun 25, 2012 at 11:16 AM, Maarten Brock <sou...@ds...>wrote: > Hi, > > > On 25. 06. 2012 02:26, Patryk wrote: > > > I was able to successfully install and run RC1/RC2 on Win98. I have > tested > > > some previous 8051 project and after some tweeks it compiled and > worked. > > > > > > Here are 2 issues spotted, not present in SDCC 3.1.0: > > > > > > 1) this may be Win98 specific - slashes in paths have doubled: > > > SDCC 3.1.0 > > > D:\MM\SiLabs_IDE\ADuC\main.c:116: warning 110: conditional flow > changed by > > > optimizer: so said EVELYN the modified DOG > > > SDCC 3.2.0 > > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: warning 110: conditional flow > changed > > > by optimizer: so said EVELYN the modified DOG > > > SDCC 3.2.0 *.asm: > > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: ERROR: No such file or directory > > > > Patryc, can you please provide a short c source file which reproduce the > > problem? Can you please add the -V sdcc command line option, run > > compilation and send the result? Specially the "No such file or > > directory" error makes me nervous: it seems that it didn't happen in > 3.1.0. > > > > I propose to open a bug report and supply / attach all the needed info > > there. > > I also noticed the double backslashes when SDCC > generates an error: > Source\\cmdintf.c:38: syntax error: token -> ';' ; > column 20 > I never noticed it: usually I'm using the forward slashes. I'll take a look where it is comming from. But I don't know where the "No such file ..." comes > from. I don't get that. Hopefully Patryk will explain it. > > 2) extern __sfr16 > > > sdcc -c test.c: > > > extern __sfr16 __at(0xCDCC) TMR2; > > > void f(void) > > > { > > > TMR2 = 0; > > > } > > > test.asm:108: Error: <r> relocation error > > > > > > No such problem with 8bit __sfr, removing "extern" also helps. > > > > Maarten, will you take a look? > > I'll take a look into this. Thanks. > > > Regards, > > > Patryk > > > > Thanks for the precious report, > > Borut > > My projects compile clean now with RC2. Size is slightly > different (some larger, some smaller). But BSEG symbols > are missing from the .map file. > What the hack????? Borut |
From: Borut R. <bor...@gm...> - 2012-06-25 11:58:53
|
On Mon, Jun 25, 2012 at 11:47 AM, Borut Ražem <bor...@gm...> wrote: > I also noticed the double backslashes when SDCC >> generates an error: >> Source\\cmdintf.c:38: syntax error: token -> ';' ; >> column 20 >> > > I never noticed it: usually I'm using the forward slashes. I'll take a > look where it is comming from. > They are comming from the preprocessor: sdcc -E Source\cmdintf.c It seems that multiple backslashes in path are treated as one on WinNT derivates and probably treated as an error on Win95 derivates, for example: dir .\\t.c is OK and treated as dir .\t.c on WinXP (verified); is treated as an error on Win98 (speculation). Can enybody confirm my speculation about Win98 behaviour? In the mean time I'll try to fix the problem by "unescaping" the file names coming from the preprocessor. Borut |
From: <pa...@wp...> - 2012-06-25 12:10:26
|
Dnia 25-06-2012 o godz. 11:47 Borut RaĹžem napisał(a): > On Mon, Jun 25, 2012 at 11:16 AM, Maarten Brock <sou...@ds...> wrote: > > > Hi, > > > > > On 25. 06. 2012 02:26, Patryk wrote: > > > > I was able to successfully install and run RC1/RC2 on Win98. I have tested > > > > some previous 8051 project and after some tweeks it compiled and worked. > > > > > > > > Here are 2 issues spotted, not present in SDCC 3.1.0: > > > > > > > > 1) this may be Win98 specific - slashes in paths have doubled: > > > > SDCC 3.1.0 > > > > D:\MM\SiLabs_IDE\ADuC\main.c:116: warning 110: conditional flow changed by > > > > optimizer: so said EVELYN the modified DOG > > > > SDCC 3.2.0 > > > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: warning 110: conditional flow changed > > > > by optimizer: so said EVELYN the modified DOG > > > > SDCC 3.2.0 *.asm: > > > > D:\\MM\\SiLabs_IDE\\ADuC\\main.c:109: ERROR: No such file or directory > > > > > > Patryc, can you please provide a short c source file which reproduce the > > > problem? Can you please add the -V sdcc command line option, run > > > compilation and send the result? Specially the "No such file or > > > directory" error makes me nervous: it seems that it didn't happen in 3.1.0. > > > > > > I propose to open a bug report and supply / attach all the needed info > > > there. I mean any SDCC warning/error during compilation, as Maarten confirmed below. It causes some confusion to SiLabs IDE. As of "No such file or directory" - it's just a line from *.asm file generated by SDCC. There should be source code cited, but double slashes seems to prevent SDCC access to the source file under Win98 during *.asm generating phase. Borut - I'm sorry to make you nervous, please rest assured that it's nothing serious :-) > > I also noticed the double backslashes when SDCC > > generates an error: > > Source\\cmdintf.c:38: syntax error: token -> ';' ; > > column 20 > I never noticed it: usually I'm using the forward slashes. I'll take a look where it is comming from. > > But I don't know where the "No such file ..." comes > > from. I don't get that. > Hopefully Patryk will explain it. > > > > 2) extern __sfr16 > > > > sdcc -c test.c: > > > > extern __sfr16 __at(0xCDCC) TMR2; > > > > void f(void) > > > > { > > > > TMR2 = 0; > > > > } > > > > test.asm:108: Error: <r> relocation error > > > > > > > > No such problem with 8bit __sfr, removing "extern" also helps. > > > > > > Maarten, will you take a look? > > > > I'll take a look into this. > Thanks. > > > > > Regards, > > > > Patryk > > > > > > Thanks for the precious report, > > > Borut > > > > My projects compile clean now with RC2. Size is slightly > > different (some larger, some smaller). But BSEG symbols > > are missing from the .map file. > What the hack????? > Borut |
From: Borut R. <bor...@gm...> - 2012-06-25 13:59:50
|
On Mon, Jun 25, 2012 at 2:10 PM, <pa...@wp...> wrote: > Dnia 25-06-2012 o godz. 11:47 Borut RaĹžem napisał(a): > > > > Patryc, can you please provide a short c source file which reproduce > the > > > > problem? Can you please add the -V sdcc command line option, run > > > > compilation and send the result? Specially the "No such file or > > > > directory" error makes me nervous: it seems that it didn't happen in > 3.1.0. > > > > > > > > I propose to open a bug report and supply / attach all the needed > info > > > > there. > > I mean any SDCC warning/error during compilation, as Maarten confirmed > below. It causes some confusion to SiLabs IDE. > As of "No such file or directory" - it's just a line from *.asm file > generated by SDCC. There should be source code cited, but double slashes > seems to prevent SDCC access to the source file under Win98 during *.asm > generating phase. Borut - I'm sorry to make you nervous, please rest > assured that it's nothing serious :-) It is not you making me nervous, it is the fact that we have a regression an that I'm probably guilty for it. :-( I would still appreciate if you can send me the output with -V option. Borut |
From: Borut R. <bor...@gm...> - 2012-06-25 15:06:01
|
On Mon, Jun 25, 2012 at 3:59 PM, Borut Ražem <bor...@gm...> wrote: > On Mon, Jun 25, 2012 at 2:10 PM, <pa...@wp...> wrote: > >> Dnia 25-06-2012 o godz. 11:47 Borut RaĹžem napisał(a): >> > > > Patryc, can you please provide a short c source file which >> reproduce the >> > > > problem? Can you please add the -V sdcc command line option, run >> > > > compilation and send the result? Specially the "No such file or >> > > > directory" error makes me nervous: it seems that it didn't happen >> in 3.1.0. >> > > > >> > > > I propose to open a bug report and supply / attach all the needed >> info >> > > > there. >> >> I mean any SDCC warning/error during compilation, as Maarten confirmed >> below. It causes some confusion to SiLabs IDE. >> As of "No such file or directory" - it's just a line from *.asm file >> generated by SDCC. There should be source code cited, but double slashes >> seems to prevent SDCC access to the source file under Win98 during *.asm >> generating phase. Borut - I'm sorry to make you nervous, please rest >> assured that it's nothing serious :-) >> > > It is not you making me nervous, it is the fact that we have a regression > an that I'm probably guilty for it. :-( > > I would still appreciate if you can send me the output with -V option. > I have the solution. I'll run regression tests locally and if everything goes well I'll commit the change. If anybody has concerns, please let me know ASAP. P.S.: I confirm that I'm gulty: I removed the call to "unescape" function copyStr() since it seemed wrong to me. Now I added a comment so it won't happen again :-( Borut |
From: Patryk <pa...@wp...> - 2012-06-25 19:33:18
|
----- Original Message ----- From: "Borut Ražem" <bor...@gm...> To: "Development chatter about sdcc" <sdc...@li...> Sent: Monday, June 25, 2012 3:59 PM Subject: Re: [sdcc-devel] SDCC 3.2.0 Release Candidate 2 On Mon, Jun 25, 2012 at 2:10 PM, <pa...@wp...> wrote: > Dnia 25-06-2012 o godz. 11:47 Borut RaĹžem napisał(a): > > > > Patryc, can you please provide a short c source file which reproduce > the > > > > problem? Can you please add the -V sdcc command line option, run > > > > compilation and send the result? Specially the "No such file or > > > > directory" error makes me nervous: it seems that it didn't happen in > 3.1.0. > > > > > > > > I propose to open a bug report and supply / attach all the needed > info > > > > there. > > I mean any SDCC warning/error during compilation, as Maarten confirmed > below. It causes some confusion to SiLabs IDE. > As of "No such file or directory" - it's just a line from *.asm file > generated by SDCC. There should be source code cited, but double slashes > seems to prevent SDCC access to the source file under Win98 during *.asm > generating phase. Borut - I'm sorry to make you nervous, please rest > assured that it's nothing serious :-) It is not you making me nervous, it is the fact that we have a regression an that I'm probably guilty for it. :-( I would still appreciate if you can send me the output with -V option. [Patryk] Here it is (RC2): SDCC : mcs51/gbz80/z80/z180/r2k/r3ka/ds390/pic16/pic14/TININative/ds400/hc08/s08 3.2.0 #7964 (Jun 24 2012) (MINGW32) Borut |