From: Philipp K. K. <pk...@sp...> - 2014-02-04 17:27:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There has been a long time since the previous release. IMO, too long. I suggest we make plans for the next release. Philipp P.S.: Congratulations on commit #8921, Maarten. I see a nice improvement in mcs51 code size. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlLxIwEACgkQbtUV+xsoLprIewCgiwMjOkox0+ULLXhqySfOw3xJ Q5IAoMf1aRR4CQYGylq4qDviKA0Y6H6Z =uOlJ -----END PGP SIGNATURE----- |
From: Philipp K. K. <pk...@sp...> - 2016-01-01 16:53:54
Attachments:
signature.asc
|
SDCC seems quite stable currently, there were no recent big changes. Since 3.5.0 we've seen the merge of current upstream binutils into our fork, bugfixes mostly for the stm8 and z80-related ports, new memory management with lower overhead, and a lot of progress in standard-compliance. IMO, this would be a good time for a 3.6.0 release. Philipp |
From: Molnár K. <car...@fr...> - 2016-01-02 09:44:18
|
On Fri, 1 Jan 2016 17:54:01 +0100 Philipp Klaus Krause <pk...@sp...> wrote: > SDCC seems quite stable currently, there were no recent big changes. > Since 3.5.0 we've seen the merge of current upstream binutils into our > fork, bugfixes mostly for the stm8 and z80-related ports, new memory > management with lower overhead, and a lot of progress in > standard-compliance. > IMO, this would be a good time for a 3.6.0 release. > > Philipp > Just now I work for on support of more new PIC processors. Large the lag compared to the gputils. Should I wait with him? Károly |
From: Philipp K. K. <pk...@sp...> - 2016-01-02 21:01:31
Attachments:
signature.asc
|
On 02.01.2016 10:44, Molnár Károly wrote: > On Fri, 1 Jan 2016 17:54:01 +0100 Philipp Klaus Krause <pk...@sp...> > wrote: > >> SDCC seems quite stable currently, there were no recent big >> changes. Since 3.5.0 we've seen the merge of current upstream >> binutils into our fork, bugfixes mostly for the stm8 and >> z80-related ports, new memory management with lower overhead, and a >> lot of progress in standard-compliance. IMO, this would be a good >> time for a 3.6.0 release. >> >> Philipp >> > > Just now I work for on support of more new PIC processors. Large the > lag compared to the gputils. Should I wait with him? > > Károly I guess continuing your work is fine. WE haven't agreed on a release schedule yet. And adding support for more PIC sounds like something that does not affect the stable backends anyway. Philipp |
From: Philipp K. K. <pk...@sp...> - 2016-01-02 21:39:38
Attachments:
signature.asc
|
On 01.01.2016 17:54, Philipp Klaus Krause wrote: > SDCC seems quite stable currently, there were no recent big changes. > Since 3.5.0 we've seen the merge of current upstream binutils into our > fork, bugfixes mostly for the stm8 and z80-related ports, new memory > management with lower overhead, and a lot of progress in > standard-compliance. > IMO, this would be a good time for a 3.6.0 release. > > Philipp For 3.5.0 the plan was 14 days from RC1 to release: 1 week for testing RC1, 1 week for testing RC2. And the plan nearly worked. Should we use the same plan for 3.6.0 again? Philipp |
From: Maarten B. <sou...@ds...> - 2016-01-03 19:28:52
|
Philipp, I seem to remember that not so long ago you changed 8 bit constants to 16 bit. I have a strong feeling this is the cause for the recent complaints about code increase, including switch statements. Before we start a release schedule, I would like to know if this is true. Since you also regularly check code sizes, can you please investigate? In the meantime, I think we should upgrade the Distributed Compile Farm with the latest gputils. It's been a long while since that was done, I think. Maarten > SDCC seems quite stable currently, there were no recent big changes. > Since 3.5.0 we've seen the merge of current upstream binutils into our > fork, bugfixes mostly for the stm8 and z80-related ports, new memory > management with lower overhead, and a lot of progress in > standard-compliance. > IMO, this would be a good time for a 3.6.0 release. > > Philipp |
From: Philipp K. K. <pk...@sp...> - 2016-01-03 20:03:15
Attachments:
signature.asc
|
On 03.01.2016 20:28, Maarten Brock wrote: > Philipp, > > I seem to remember that not so long ago you changed 8 bit constants to 16 > bit. Yes. I changed the type of character constants from char to int. For the situations I looked at back then it did not matter for code size. > I have a strong feeling this is the cause for the recent complaints > about code increase, including switch statements. Before we start a > release schedule, I would like to know if this is true. Since you also > regularly check code sizes, can you please investigate? As soon as I find some time. I hope to be able to have a closer look sometime wednesday. Philipp |
From: Philipp K. K. <pk...@sp...> - 2016-01-11 10:01:46
Attachments:
signature.asc
|
On 03.01.2016 20:28, Maarten Brock wrote: > Philipp, > > I seem to remember that not so long ago you changed 8 bit constants to 16 > bit. I have a strong feeling this is the cause for the recent complaints > about code increase, including switch statements. Before we start a > release schedule, I would like to know if this is true. Since you also > regularly check code sizes, can you please investigate? I'd consider this issue sufficiently resolved for a release. There are some corner cases with code size increase remaining. But the optimizations I subsequently introduced fixed nearly all code size regressions from making character literals int. And they resulted in further code size reductions, so that in total, code size is now smaller than before. > > In the meantime, I think we should upgrade the Distributed Compile Farm > with the latest gputils. It's been a long while since that was done, I > think. Sounds like a good thing to do, but probably a task for someone who knows the compile farm and gputilsbetter than me. Regression test results look ok to me. We've had a few further bug fixes, and support or more pic devices, but no really big changes recently. Philipp |
From: ESSAISSI, R. J. <re...@re...> - 2016-01-11 10:37:20
|
Dear Mr / Ms, I dont understand why none of the coders, especially for the assemblers didnt answer back, someone has wrote them right ? I asked for a road map, to implement utf8 support in the assemblers, I had no answers so far . I looked in the source ... couldnt find where to start yet. and no it is not only to make reading the assembly code easier , but also, to make writing assembly , "easier" . which is, for many a standard and a must , in the 8bit world , I consider that whoever works with 8bit MCUs , without knowing and/or beeing intersted in the it s assembly language ... is just a little "low" , Besides of some 3rd world countries with their technological embargos , many use 8bit MCUs for the footprint (hardware and software) , and that cannot be achieved with at least some assembly awareness. Hence, I dont understand theses non-interested in my initiative -- and by their makers (whom who wrote the assemblers). Met vriendelijke groet ESSAISSI, Rémi Julien On Monday, 11-01-2016 at 11:01 Philipp Klaus Krause wrote: On 03.01.2016 20:28, Maarten Brock wrote: > Philipp, > > I seem to remember that not so long ago you changed 8 bit constants to 16 > bit. I have a strong feeling this is the cause for the recent complaints > about code increase, including switch statements. Before we start a > release schedule, I would like to know if this is true. Since you also > regularly check code sizes, can you please investigate? I'd consider this issue sufficiently resolved for a release. There are some corner cases with code size increase remaining. But the optimizations I subsequently introduced fixed nearly all code size regressions from making character literals int. And they resulted in further code size reductions, so that in total, code size is now smaller than before. > > In the meantime, I think we should upgrade the Distributed Compile Farm > with the latest gputils. It's been a long while since that was done, I > think. Sounds like a good thing to do, but probably a task for someone who knows the compile farm and gputilsbetter than me. Regression test results look ok to me. We've had a few further bug fixes, and support or more pic devices, but no really big changes recently. Philipp ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ sdcc-devel mailing list sdc...@li... https://lists.sourceforge.net/lists/listinfo/sdcc-devel |
From: Erik P. <epe...@iv...> - 2016-01-12 09:50:18
|
On Mon, 11 Jan 2016, Philipp Klaus Krause wrote: > On 03.01.2016 20:28, Maarten Brock wrote: [snip] >> >> In the meantime, I think we should upgrade the Distributed Compile Farm >> with the latest gputils. It's been a long while since that was done, I >> think. > > Sounds like a good thing to do, but probably a task for someone who > knows the compile farm and gputils better than me. cf-x86, cf-i386-debian, and cf-ppc-macosx have all been updated to the recent gputils 1.4.2-1 release. This covers the Linux 32-bit, Linux 64-bit, Windows 32-bit, Windows 64-bit, and Mac OS X 32-bit univeral Intel/PPC snapshot builds. Erik |
From: Philipp K. K. <pk...@sp...> - 2016-04-12 20:44:01
Attachments:
signature.asc
|
On 01.01.2016 17:54, Philipp Klaus Krause wrote: > SDCC seems quite stable currently, there were no recent big changes. > Since 3.5.0 we've seen the merge of current upstream binutils into our > fork, bugfixes mostly for the stm8 and z80-related ports, new memory > management with lower overhead, and a lot of progress in > standard-compliance. > IMO, this would be a good time for a 3.6.0 release. > > Philipp > 2½ months have passed. And the list at http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List has become quite long. We have a lot of new features and important bug fixes since 3.5.0. Philipp |
From: Maarten B. <sou...@ds...> - 2016-04-16 18:44:41
|
> On 01.01.2016 17:54, Philipp Klaus Krause wrote: >> SDCC seems quite stable currently, there were no recent big changes. >> Since 3.5.0 we've seen the merge of current upstream binutils into our >> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >> management with lower overhead, and a lot of progress in >> standard-compliance. >> IMO, this would be a good time for a 3.6.0 release. >> >> Philipp >> > > 2½ months have passed. And the list at > > http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List > > has become quite long. We have a lot of new features and important bug > fixes since 3.5.0. > > Philipp I'm looking into the stability of SDCC. Currently make distclean fails: $ make distclean > /dev/null make[3]: [distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. And afterwards svn status shows remaining files: $ svn status ? device/lib/gbz80/setjmp.s ? device/lib/pic14/.checksupport ? device/lib/pic14/a.cod ? device/lib/pic14/a.hex ? device/lib/pic16/.checkdevices ? device/lib/pic16/a.cod ? device/lib/pic16/a.hex ? device/lib/pic16/pics.supported ? device/non-free/lib/pic14/.checkdevices ? device/non-free/lib/pic14/a.cod ? device/non-free/lib/pic14/a.hex ? device/non-free/lib/pic14/a.lst ? device/non-free/lib/pic14/pics.supported ? device/non-free/lib/pic16/.checkdevices ? device/non-free/lib/pic16/a.cod ? device/non-free/lib/pic16/a.hex ? device/non-free/lib/pic16/pics.supported ? support/sdbinutils/bfd/doc/bfd.info ? support/sdbinutils/binutils/arlex.c ? support/sdbinutils/binutils/arparse.c ? support/sdbinutils/binutils/arparse.h ? support/sdbinutils/binutils/defparse.c ? support/sdbinutils/binutils/defparse.h ? support/sdbinutils/binutils/mcparse.c ? support/sdbinutils/binutils/mcparse.h ? support/sdbinutils/binutils/rcparse.c ? support/sdbinutils/binutils/rcparse.h ? support/sdbinutils/binutils/sysinfo.c ? support/sdbinutils/binutils/sysinfo.h ? support/sdbinutils/binutils/syslex.c ? support/tests/isdigit.c This requires fixing. If anyone has the time to look into this, please say so. Otherwise I will dive into this myself. In the meantime I'm fixing some other warnings that seem to be ignored. I'm repeating myself here: build SDCC with "make > /dev/null" so you actually can see the warnings! Maarten |
From: 史斌 <pow...@16...> - 2016-04-16 22:31:24
|
Which version of gcc are you currently using? I always get huge mount of warnings with gcc 4.9 and newest clang. Ben Shi 在 2016年4月17日,02:44,Maarten Brock <sou...@ds...> 写道: >> On 01.01.2016 17:54, Philipp Klaus Krause wrote: >>> SDCC seems quite stable currently, there were no recent big changes. >>> Since 3.5.0 we've seen the merge of current upstream binutils into our >>> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >>> management with lower overhead, and a lot of progress in >>> standard-compliance. >>> IMO, this would be a good time for a 3.6.0 release. >>> >>> Philipp >> >> 2½ months have passed. And the list at >> >> http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List >> >> has become quite long. We have a lot of new features and important bug >> fixes since 3.5.0. >> >> Philipp > > I'm looking into the stability of SDCC. Currently make distclean fails: > > $ make distclean > /dev/null > make[3]: [distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > > And afterwards svn status shows remaining files: > > $ svn status > ? device/lib/gbz80/setjmp.s > ? device/lib/pic14/.checksupport > ? device/lib/pic14/a.cod > ? device/lib/pic14/a.hex > ? device/lib/pic16/.checkdevices > ? device/lib/pic16/a.cod > ? device/lib/pic16/a.hex > ? device/lib/pic16/pics.supported > ? device/non-free/lib/pic14/.checkdevices > ? device/non-free/lib/pic14/a.cod > ? device/non-free/lib/pic14/a.hex > ? device/non-free/lib/pic14/a.lst > ? device/non-free/lib/pic14/pics.supported > ? device/non-free/lib/pic16/.checkdevices > ? device/non-free/lib/pic16/a.cod > ? device/non-free/lib/pic16/a.hex > ? device/non-free/lib/pic16/pics.supported > ? support/sdbinutils/bfd/doc/bfd.info > ? support/sdbinutils/binutils/arlex.c > ? support/sdbinutils/binutils/arparse.c > ? support/sdbinutils/binutils/arparse.h > ? support/sdbinutils/binutils/defparse.c > ? support/sdbinutils/binutils/defparse.h > ? support/sdbinutils/binutils/mcparse.c > ? support/sdbinutils/binutils/mcparse.h > ? support/sdbinutils/binutils/rcparse.c > ? support/sdbinutils/binutils/rcparse.h > ? support/sdbinutils/binutils/sysinfo.c > ? support/sdbinutils/binutils/sysinfo.h > ? support/sdbinutils/binutils/syslex.c > ? support/tests/isdigit.c > > This requires fixing. If anyone has the time to look into this, please say > so. Otherwise I will dive into this myself. > > In the meantime I'm fixing some other warnings that seem to be ignored. > I'm repeating myself here: build SDCC with "make > /dev/null" so you > actually can see the warnings! > > Maarten > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel |
From: Maarten B. <sou...@ds...> - 2016-04-16 23:10:55
|
Hi Ben, I use gcc 4.8.4 on Ubuntu LTS. I'm working on warnings that sdcc generates. Maarten > Which version of gcc are you currently using? > > I always get huge mount of warnings with gcc 4.9 and newest clang. > > > > Ben Shi > > å¨ 2016å¹´4æ17æ¥ï¼02:44ï¼Maarten Brock <sou...@ds...> > åéï¼ > >>> On 01.01.2016 17:54, Philipp Klaus Krause wrote: >>>> SDCC seems quite stable currently, there were no recent big changes. >>>> Since 3.5.0 we've seen the merge of current upstream binutils into our >>>> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >>>> management with lower overhead, and a lot of progress in >>>> standard-compliance. >>>> IMO, this would be a good time for a 3.6.0 release. >>>> >>>> Philipp >>> >>> 2½ months have passed. And the list at >>> >>> http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List >>> >>> has become quite long. We have a lot of new features and important bug >>> fixes since 3.5.0. >>> >>> Philipp >> >> I'm looking into the stability of SDCC. Currently make distclean fails: >> >> $ make distclean > /dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> >> And afterwards svn status shows remaining files: >> >> $ svn status >> ? device/lib/gbz80/setjmp.s >> ? device/lib/pic14/.checksupport >> ? device/lib/pic14/a.cod >> ? device/lib/pic14/a.hex >> ? device/lib/pic16/.checkdevices >> ? device/lib/pic16/a.cod >> ? device/lib/pic16/a.hex >> ? device/lib/pic16/pics.supported >> ? device/non-free/lib/pic14/.checkdevices >> ? device/non-free/lib/pic14/a.cod >> ? device/non-free/lib/pic14/a.hex >> ? device/non-free/lib/pic14/a.lst >> ? device/non-free/lib/pic14/pics.supported >> ? device/non-free/lib/pic16/.checkdevices >> ? device/non-free/lib/pic16/a.cod >> ? device/non-free/lib/pic16/a.hex >> ? device/non-free/lib/pic16/pics.supported >> ? support/sdbinutils/bfd/doc/bfd.info >> ? support/sdbinutils/binutils/arlex.c >> ? support/sdbinutils/binutils/arparse.c >> ? support/sdbinutils/binutils/arparse.h >> ? support/sdbinutils/binutils/defparse.c >> ? support/sdbinutils/binutils/defparse.h >> ? support/sdbinutils/binutils/mcparse.c >> ? support/sdbinutils/binutils/mcparse.h >> ? support/sdbinutils/binutils/rcparse.c >> ? support/sdbinutils/binutils/rcparse.h >> ? support/sdbinutils/binutils/sysinfo.c >> ? support/sdbinutils/binutils/sysinfo.h >> ? support/sdbinutils/binutils/syslex.c >> ? support/tests/isdigit.c >> >> This requires fixing. If anyone has the time to look into this, please >> say >> so. Otherwise I will dive into this myself. >> >> In the meantime I'm fixing some other warnings that seem to be ignored. >> I'm repeating myself here: build SDCC with "make > /dev/null" so you >> actually can see the warnings! >> >> Maarten |
From: Molnár K. <car...@fr...> - 2016-04-17 19:22:20
|
On Sat, 16 Apr 2016 20:44:47 +0200 (CEST) "Maarten Brock" <sou...@ds...> wrote: > > On 01.01.2016 17:54, Philipp Klaus Krause wrote: > >> SDCC seems quite stable currently, there were no recent big changes. > >> Since 3.5.0 we've seen the merge of current upstream binutils into our > >> fork, bugfixes mostly for the stm8 and z80-related ports, new memory > >> management with lower overhead, and a lot of progress in > >> standard-compliance. > >> IMO, this would be a good time for a 3.6.0 release. > >> > >> Philipp > >> > > > > 2½ months have passed. And the list at > > > > http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List > > > > has become quite long. We have a lot of new features and important bug > > fixes since 3.5.0. > > > > Philipp > > I'm looking into the stability of SDCC. Currently make distclean fails: > > $ make distclean > /dev/null > make[3]: [distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > > And afterwards svn status shows remaining files: > > $ svn status > ? device/lib/gbz80/setjmp.s > ? device/lib/pic14/.checksupport > ? device/lib/pic14/a.cod > ? device/lib/pic14/a.hex > ? device/lib/pic16/.checkdevices > ? device/lib/pic16/a.cod > ? device/lib/pic16/a.hex > ? device/lib/pic16/pics.supported > ? device/non-free/lib/pic14/.checkdevices > ? device/non-free/lib/pic14/a.cod > ? device/non-free/lib/pic14/a.hex > ? device/non-free/lib/pic14/a.lst > ? device/non-free/lib/pic14/pics.supported > ? device/non-free/lib/pic16/.checkdevices > ? device/non-free/lib/pic16/a.cod > ? device/non-free/lib/pic16/a.hex > ? device/non-free/lib/pic16/pics.supported The PIC processor-related bug fixed in the [r9568] version. Károly > ? support/sdbinutils/bfd/doc/bfd.info > ? support/sdbinutils/binutils/arlex.c > ? support/sdbinutils/binutils/arparse.c > ? support/sdbinutils/binutils/arparse.h > ? support/sdbinutils/binutils/defparse.c > ? support/sdbinutils/binutils/defparse.h > ? support/sdbinutils/binutils/mcparse.c > ? support/sdbinutils/binutils/mcparse.h > ? support/sdbinutils/binutils/rcparse.c > ? support/sdbinutils/binutils/rcparse.h > ? support/sdbinutils/binutils/sysinfo.c > ? support/sdbinutils/binutils/sysinfo.h > ? support/sdbinutils/binutils/syslex.c > ? support/tests/isdigit.c > > This requires fixing. If anyone has the time to look into this, please say > so. Otherwise I will dive into this myself. > > In the meantime I'm fixing some other warnings that seem to be ignored. > I'm repeating myself here: build SDCC with "make > /dev/null" so you > actually can see the warnings! > > Maarten > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Maarten B. <sou...@ds...> - 2016-04-18 22:12:52
|
> On Sat, 16 Apr 2016 20:44:47 +0200 (CEST) > "Maarten Brock" <sou...@ds...> wrote: > >> > On 01.01.2016 17:54, Philipp Klaus Krause wrote: >> >> SDCC seems quite stable currently, there were no recent big changes. >> >> Since 3.5.0 we've seen the merge of current upstream binutils into >> our >> >> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >> >> management with lower overhead, and a lot of progress in >> >> standard-compliance. >> >> IMO, this would be a good time for a 3.6.0 release. >> >> >> >> Philipp >> >> >> > >> > 2½ months have passed. And the list at >> > >> > http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List >> > >> > has become quite long. We have a lot of new features and important bug >> > fixes since 3.5.0. >> > >> > Philipp >> >> I'm looking into the stability of SDCC. Currently make distclean fails: >> >> $ make distclean > /dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> >> And afterwards svn status shows remaining files: >> >> $ svn status >> ? device/lib/gbz80/setjmp.s > >> ? device/lib/pic14/.checksupport >> ? device/lib/pic14/a.cod >> ? device/lib/pic14/a.hex >> ? device/lib/pic16/.checkdevices >> ? device/lib/pic16/a.cod >> ? device/lib/pic16/a.hex >> ? device/lib/pic16/pics.supported >> ? device/non-free/lib/pic14/.checkdevices >> ? device/non-free/lib/pic14/a.cod >> ? device/non-free/lib/pic14/a.hex >> ? device/non-free/lib/pic14/a.lst >> ? device/non-free/lib/pic14/pics.supported >> ? device/non-free/lib/pic16/.checkdevices >> ? device/non-free/lib/pic16/a.cod >> ? device/non-free/lib/pic16/a.hex >> ? device/non-free/lib/pic16/pics.supported > > The PIC processor-related bug fixed in the [r9568] version. > > Károly > >> ? support/sdbinutils/bfd/doc/bfd.info >> ? support/sdbinutils/binutils/arlex.c >> ? support/sdbinutils/binutils/arparse.c >> ? support/sdbinutils/binutils/arparse.h >> ? support/sdbinutils/binutils/defparse.c >> ? support/sdbinutils/binutils/defparse.h >> ? support/sdbinutils/binutils/mcparse.c >> ? support/sdbinutils/binutils/mcparse.h >> ? support/sdbinutils/binutils/rcparse.c >> ? support/sdbinutils/binutils/rcparse.h >> ? support/sdbinutils/binutils/sysinfo.c >> ? support/sdbinutils/binutils/sysinfo.h >> ? support/sdbinutils/binutils/syslex.c >> ? support/tests/isdigit.c >> >> This requires fixing. If anyone has the time to look into this, please >> say so. Otherwise I will dive into this myself. >> >> In the meantime I'm fixing some other warnings that seem to be ignored. >> I'm repeating myself here: build SDCC with "make > /dev/null" so you >> actually can see the warnings! >> >> Maarten I still have the following during a make: $ make -j6 > /dev/null /home/maarten/sdcc-pure/support/sdbinutils/binutils/sysinfo.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] /home/maarten/sdcc-pure/support/sdbinutils/binutils/defparse.y: warning: 27 shift/reduce conflicts [-Wconflicts-sr] /home/maarten/sdcc-pure/support/sdbinutils/binutils/mcparse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] /home/maarten/sdcc-pure/support/sdbinutils/binutils/rcparse.y: warning: 58 shift/reduce conflicts [-Wconflicts-sr] /home/maarten/sdcc-pure/support/sdbinutils/binutils/rcparse.y: warning: 10 reduce/reduce conflicts [-Wconflicts-rr] tinibios.c:103: warning 158: overflow in implicit constant conversion main::scan_file() called too early to check prototype at /usr/bin/aclocal-1.11 line 643. And then during make distclean: $ make distclean > /dev/null make[3]: [distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. And then svn status gives: $ svn status ? support/sdbinutils/bfd/doc/bfd.info ? support/sdbinutils/binutils/arlex.c ? support/sdbinutils/binutils/arparse.c ? support/sdbinutils/binutils/arparse.h ? support/sdbinutils/binutils/defparse.c ? support/sdbinutils/binutils/defparse.h ? support/sdbinutils/binutils/mcparse.c ? support/sdbinutils/binutils/mcparse.h ? support/sdbinutils/binutils/rcparse.c ? support/sdbinutils/binutils/rcparse.h ? support/sdbinutils/binutils/sysinfo.c ? support/sdbinutils/binutils/sysinfo.h ? support/sdbinutils/binutils/syslex.c Maarten |
From: Molnár K. <car...@fr...> - 2016-04-19 07:16:05
|
On Tue, 19 Apr 2016 00:12:56 +0200 (CEST) "Maarten Brock" <sou...@ds...> wrote: > > On Sat, 16 Apr 2016 20:44:47 +0200 (CEST) > > "Maarten Brock" <sou...@ds...> wrote: > > > >> > On 01.01.2016 17:54, Philipp Klaus Krause wrote: > >> >> SDCC seems quite stable currently, there were no recent big changes. > >> >> Since 3.5.0 we've seen the merge of current upstream binutils into > >> our > >> >> fork, bugfixes mostly for the stm8 and z80-related ports, new memory > >> >> management with lower overhead, and a lot of progress in > >> >> standard-compliance. > >> >> IMO, this would be a good time for a 3.6.0 release. > >> >> > >> >> Philipp > >> >> > >> > > >> > 2½ months have passed. And the list at > >> > > >> > http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List > >> > > >> > has become quite long. We have a lot of new features and important bug > >> > fixes since 3.5.0. > >> > > >> > Philipp > >> > >> I'm looking into the stability of SDCC. Currently make distclean fails: > >> > >> $ make distclean > /dev/null > >> make[3]: [distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> > >> And afterwards svn status shows remaining files: > >> > >> $ svn status > >> ? device/lib/gbz80/setjmp.s > > > >> ? device/lib/pic14/.checksupport > >> ? device/lib/pic14/a.cod > >> ? device/lib/pic14/a.hex > >> ? device/lib/pic16/.checkdevices > >> ? device/lib/pic16/a.cod > >> ? device/lib/pic16/a.hex > >> ? device/lib/pic16/pics.supported > >> ? device/non-free/lib/pic14/.checkdevices > >> ? device/non-free/lib/pic14/a.cod > >> ? device/non-free/lib/pic14/a.hex > >> ? device/non-free/lib/pic14/a.lst > >> ? device/non-free/lib/pic14/pics.supported > >> ? device/non-free/lib/pic16/.checkdevices > >> ? device/non-free/lib/pic16/a.cod > >> ? device/non-free/lib/pic16/a.hex > >> ? device/non-free/lib/pic16/pics.supported > > > > The PIC processor-related bug fixed in the [r9568] version. > > > > Károly > > > >> ? support/sdbinutils/bfd/doc/bfd.info > >> ? support/sdbinutils/binutils/arlex.c > >> ? support/sdbinutils/binutils/arparse.c > >> ? support/sdbinutils/binutils/arparse.h > >> ? support/sdbinutils/binutils/defparse.c > >> ? support/sdbinutils/binutils/defparse.h > >> ? support/sdbinutils/binutils/mcparse.c > >> ? support/sdbinutils/binutils/mcparse.h > >> ? support/sdbinutils/binutils/rcparse.c > >> ? support/sdbinutils/binutils/rcparse.h > >> ? support/sdbinutils/binutils/sysinfo.c > >> ? support/sdbinutils/binutils/sysinfo.h > >> ? support/sdbinutils/binutils/syslex.c > >> ? support/tests/isdigit.c > >> > >> This requires fixing. If anyone has the time to look into this, please > >> say so. Otherwise I will dive into this myself. > >> > >> In the meantime I'm fixing some other warnings that seem to be ignored. > >> I'm repeating myself here: build SDCC with "make > /dev/null" so you > >> actually can see the warnings! > >> > >> Maarten > > I still have the following during a make: > > $ make -j6 > /dev/null > /home/maarten/sdcc-pure/support/sdbinutils/binutils/sysinfo.y: warning: 1 > shift/reduce conflict [-Wconflicts-sr] > /home/maarten/sdcc-pure/support/sdbinutils/binutils/defparse.y: warning: > 27 shift/reduce conflicts [-Wconflicts-sr] > /home/maarten/sdcc-pure/support/sdbinutils/binutils/mcparse.y: warning: 1 > shift/reduce conflict [-Wconflicts-sr] > /home/maarten/sdcc-pure/support/sdbinutils/binutils/rcparse.y: warning: 58 > shift/reduce conflicts [-Wconflicts-sr] > /home/maarten/sdcc-pure/support/sdbinutils/binutils/rcparse.y: warning: 10 > reduce/reduce conflicts [-Wconflicts-rr] > tinibios.c:103: warning 158: overflow in implicit constant conversion > main::scan_file() called too early to check prototype at > /usr/bin/aclocal-1.11 line 643. > > And then during make distclean: > > $ make distclean > /dev/null > make[3]: [distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > > And then svn status gives: > This bug fixed in the [r9573] version. Károly > $ svn status > ? support/sdbinutils/bfd/doc/bfd.info > ? support/sdbinutils/binutils/arlex.c > ? support/sdbinutils/binutils/arparse.c > ? support/sdbinutils/binutils/arparse.h > ? support/sdbinutils/binutils/defparse.c > ? support/sdbinutils/binutils/defparse.h > ? support/sdbinutils/binutils/mcparse.c > ? support/sdbinutils/binutils/mcparse.h > ? support/sdbinutils/binutils/rcparse.c > ? support/sdbinutils/binutils/rcparse.h > ? support/sdbinutils/binutils/sysinfo.c > ? support/sdbinutils/binutils/sysinfo.h > ? support/sdbinutils/binutils/syslex.c > > Maarten > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Maarten B. <sou...@ds...> - 2016-04-20 20:15:38
|
>> And then during make distclean: >> >> $ make distclean > /dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. > > This bug fixed in the [r9573] version. > > Karoly I hate to contradict you, but this really is not fixed. $ make distclean > /dev/null make[3]: [distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: [local-distclean] Error 1 (ignored) make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. make[1]: *** No rule to make target `distclean'. Stop. $ svn update Updating '.': At revision 9574. Here is the context where the errors occur: make[3]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' make[4]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' rm -f test-demangle rm -f test-pexecute rm -f test-expandargv rm -f demangler-fuzzer rm -f core rm -f Makefile make[4]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' make SUBDIRS="" clean make[4]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' make SUBDIRS="" mostlyclean make[5]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' rm -rf *.o pic noasan core errs \#* *.E a.out rm -f errors dummy config.h stamp-* rm -f stamp-picdir stamp-noasandir rm -f libiberty.aux libiberty.cp libiberty.cps libiberty.fn libiberty.ky rm -f libiberty.log libiberty.tmp libiberty.tps libiberty.pg rm -f libiberty.pgs libiberty.toc libiberty.tp libiberty.tpl libiberty.vr rm -f libtexi.stamp make[5]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' rm -f *.a required-list tmpmulti.out rm -f libiberty.dvi libiberty.pdf libiberty.info* libiberty.html make[4]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' rm -f *~ Makefile config.cache config.status xhost-mkfrag TAGS multilib.out rm -f config.log rmdir testsuite 2>/dev/null make[3]: [distclean] Error 1 (ignored) make[3]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' make[1]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' make[2]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' make[2]: Nothing to be done for `distclean-target'. make[2]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log rm -f Makefile config.status config.cache mh-frag mt-frag rm -f maybedep.tmp serdep.tmp if [ "x86_64-unknown-linux-gnu" != "." ]; then \ rm -rf x86_64-unknown-linux-gnu; \ else true; fi rm -rf build-x86_64-unknown-linux-gnu if [ "." != "." ]; then \ rm -rf .; \ else true; fi rm -f texinfo/po/Makefile texinfo/po/Makefile.in texinfo/info/Makefile rm -f texinfo/doc/Makefile texinfo/po/POTFILES rmdir texinfo/doc texinfo/info texinfo/intl texinfo/lib 2>/dev/null make[1]: [local-distclean] Error 1 (ignored) rmdir texinfo/makeinfo texinfo/po texinfo/util 2>/dev/null make[1]: [local-distclean] Error 1 (ignored) rmdir fastjar gcc libiberty texinfo zlib 2>/dev/null make[1]: [local-distclean] Error 1 (ignored) find . -name config.cache -exec rm -f {} \; \; 2>/dev/null make[1]: [local-distclean] Error 1 (ignored) make[1]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdas6808 rm -f *.dep rm -f obj/m08pst.o obj/m08mch.o obj/m08adr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' make[1]: *** No rule to make target `distclean'. Stop. make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asstm8' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdas6808 rm -f *.dep rm -f obj/stm8pst.o obj/stm8mch.o obj/stm8adr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asstm8' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdas390 rm -f *.dep rm -f obj/ds8pst.o obj/ds8mch.o obj/ds8adr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' make[1]: *** No rule to make target `distclean'. Stop. make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8051' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdas8051 rm -f *.dep rm -f obj/i51pst.o obj/i51mch.o obj/i51adr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8051' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdasz80 rm -f *.dep rm -f obj/z80pst.o obj/z80mch.o obj/z80adr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' make[1]: *** No rule to make target `distclean'. Stop. make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' rm -f *core *[%~] *.[oa] rm -f .[a-z]*~ rm -f ../../bin/sdasrab rm -f *.dep rm -f obj/rabpst.o obj/rabmch.o obj/rabadr.o obj/asdbg.o obj/asdata.o obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o obj/dbuf_string.o obj/.stamp if [ -d obj ]; then rmdir obj; fi rm -f Makefile make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' make[1]: *** No rule to make target `distclean'. Stop. make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' Maarten |
From: Molnár K. <car...@fr...> - 2016-04-21 06:55:35
|
On Wed, 20 Apr 2016 22:15:42 +0200 (CEST) "Maarten Brock" <sou...@ds...> wrote: > >> And then during make distclean: > >> > >> $ make distclean > /dev/null > >> make[3]: [distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > > > > This bug fixed in the [r9573] version. > > > > Karoly > > I hate to contradict you, but this really is not fixed. > I withdrew the faulty bugfix. > $ make distclean > /dev/null > make[3]: [distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: *** No rule to make target `distclean'. Stop. > > $ svn update > Updating '.': > At revision 9574. > > Here is the context where the errors occur: > > > make[3]: Entering directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > make[4]: Entering directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' > rm -f test-demangle > rm -f test-pexecute > rm -f test-expandargv > rm -f demangler-fuzzer > rm -f core > rm -f Makefile > make[4]: Leaving directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' > make SUBDIRS="" clean > make[4]: Entering directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > make SUBDIRS="" mostlyclean > make[5]: Entering directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > rm -rf *.o pic noasan core errs \#* *.E a.out > rm -f errors dummy config.h stamp-* > rm -f stamp-picdir stamp-noasandir > rm -f libiberty.aux libiberty.cp libiberty.cps libiberty.fn libiberty.ky > rm -f libiberty.log libiberty.tmp libiberty.tps libiberty.pg > rm -f libiberty.pgs libiberty.toc libiberty.tp libiberty.tpl libiberty.vr > rm -f libtexi.stamp > make[5]: Leaving directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > rm -f *.a required-list tmpmulti.out > rm -f libiberty.dvi libiberty.pdf libiberty.info* libiberty.html > make[4]: Leaving directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > rm -f *~ Makefile config.cache config.status xhost-mkfrag TAGS multilib.out > rm -f config.log > rmdir testsuite 2>/dev/null > make[3]: [distclean] Error 1 (ignored) > make[3]: Leaving directory > `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > > > > make[1]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' > make[2]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' > make[2]: Nothing to be done for `distclean-target'. > make[2]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' > rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log > rm -f Makefile config.status config.cache mh-frag mt-frag > rm -f maybedep.tmp serdep.tmp > if [ "x86_64-unknown-linux-gnu" != "." ]; then \ > rm -rf x86_64-unknown-linux-gnu; \ > else true; fi > rm -rf build-x86_64-unknown-linux-gnu > if [ "." != "." ]; then \ > rm -rf .; \ > else true; fi > rm -f texinfo/po/Makefile texinfo/po/Makefile.in texinfo/info/Makefile > rm -f texinfo/doc/Makefile texinfo/po/POTFILES > rmdir texinfo/doc texinfo/info texinfo/intl texinfo/lib 2>/dev/null > make[1]: [local-distclean] Error 1 (ignored) > rmdir texinfo/makeinfo texinfo/po texinfo/util 2>/dev/null > make[1]: [local-distclean] Error 1 (ignored) > rmdir fastjar gcc libiberty texinfo zlib 2>/dev/null > make[1]: [local-distclean] Error 1 (ignored) > find . -name config.cache -exec rm -f {} \; \; 2>/dev/null > make[1]: [local-distclean] Error 1 (ignored) > make[1]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' > > > > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdas6808 > rm -f *.dep > rm -f obj/m08pst.o obj/m08mch.o obj/m08adr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asstm8' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdas6808 > rm -f *.dep > rm -f obj/stm8pst.o obj/stm8mch.o obj/stm8adr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asstm8' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdas390 > rm -f *.dep > rm -f obj/ds8pst.o obj/ds8mch.o obj/ds8adr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8051' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdas8051 > rm -f *.dep > rm -f obj/i51pst.o obj/i51mch.o obj/i51adr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8051' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdasz80 > rm -f *.dep > rm -f obj/z80pst.o obj/z80mch.o obj/z80adr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' > rm -f *core *[%~] *.[oa] > rm -f .[a-z]*~ > rm -f ../../bin/sdasrab > rm -f *.dep > rm -f obj/rabpst.o obj/rabmch.o obj/rabadr.o obj/asdbg.o obj/asdata.o > obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o obj/dbuf.o > obj/dbuf_string.o obj/.stamp > if [ -d obj ]; then rmdir obj; fi > rm -f Makefile > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' > make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' > make[1]: *** No rule to make target `distclean'. Stop. > make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' > > > Maarten > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Maarten B. <sou...@ds...> - 2016-05-02 17:39:32
|
Karoly and others, I did not mean to say that your fix was wrong. Just that it did not fix the problems that you seemed to claim that it fixed. Anyway, I'll have a deeper look. I also just installed a new version of Ubuntu 16.04 LTS. This comes with a much newer kernel (4.4) and newer tools like gcc 5.3.1. The problem I now see is a segmentation fault in the host regression tests: gcc-torture-execute-20010403-1 (f: 0, t: 0, c: 1, b: 0, T: 0) Segmentation fault (core dumped) (f: 0, t: 0, c: 0, b: 0, T: 0) gcc-torture-execute-20010422-1 (f: 0, t: 0, c: 1, b: 0, T: 0) It's probably gcc-torture-execute-20010409-1 that fails here. N.B. It is not noted in the summary! I never saw this on my older Ubuntu 14.04 with 3.13 kernel and gcc 4.8.4. Maarten > On Wed, 20 Apr 2016 22:15:42 +0200 (CEST) > "Maarten Brock" <sou...@ds...> wrote: > >> >> And then during make distclean: >> >> >> >> $ make distclean > /dev/null >> >> make[3]: [distclean] Error 1 (ignored) >> >> make[1]: [local-distclean] Error 1 (ignored) >> >> make[1]: [local-distclean] Error 1 (ignored) >> >> make[1]: [local-distclean] Error 1 (ignored) >> >> make[1]: [local-distclean] Error 1 (ignored) >> >> make[1]: *** No rule to make target `distclean'. Stop. >> >> make[1]: *** No rule to make target `distclean'. Stop. >> >> make[1]: *** No rule to make target `distclean'. Stop. >> >> make[1]: *** No rule to make target `distclean'. Stop. >> > >> > This bug fixed in the [r9573] version. >> > >> > Karoly >> >> I hate to contradict you, but this really is not fixed. >> > > I withdrew the faulty bugfix. > >> $ make distclean > /dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: *** No rule to make target `distclean'. Stop. >> >> $ svn update >> Updating '.': >> At revision 9574. >> >> Here is the context where the errors occur: >> >> >> make[3]: Entering directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> make[4]: Entering directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' >> rm -f test-demangle >> rm -f test-pexecute >> rm -f test-expandargv >> rm -f demangler-fuzzer >> rm -f core >> rm -f Makefile >> make[4]: Leaving directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' >> make SUBDIRS="" clean >> make[4]: Entering directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> make SUBDIRS="" mostlyclean >> make[5]: Entering directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> rm -rf *.o pic noasan core errs \#* *.E a.out >> rm -f errors dummy config.h stamp-* >> rm -f stamp-picdir stamp-noasandir >> rm -f libiberty.aux libiberty.cp libiberty.cps libiberty.fn libiberty.ky >> rm -f libiberty.log libiberty.tmp libiberty.tps libiberty.pg >> rm -f libiberty.pgs libiberty.toc libiberty.tp libiberty.tpl >> libiberty.vr >> rm -f libtexi.stamp >> make[5]: Leaving directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> rm -f *.a required-list tmpmulti.out >> rm -f libiberty.dvi libiberty.pdf libiberty.info* libiberty.html >> make[4]: Leaving directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> rm -f *~ Makefile config.cache config.status xhost-mkfrag TAGS >> multilib.out >> rm -f config.log >> rmdir testsuite 2>/dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[3]: Leaving directory >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' >> >> >> >> make[1]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' >> make[2]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' >> make[2]: Nothing to be done for `distclean-target'. >> make[2]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' >> rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log >> rm -f Makefile config.status config.cache mh-frag mt-frag >> rm -f maybedep.tmp serdep.tmp >> if [ "x86_64-unknown-linux-gnu" != "." ]; then \ >> rm -rf x86_64-unknown-linux-gnu; \ >> else true; fi >> rm -rf build-x86_64-unknown-linux-gnu >> if [ "." != "." ]; then \ >> rm -rf .; \ >> else true; fi >> rm -f texinfo/po/Makefile texinfo/po/Makefile.in texinfo/info/Makefile >> rm -f texinfo/doc/Makefile texinfo/po/POTFILES >> rmdir texinfo/doc texinfo/info texinfo/intl texinfo/lib 2>/dev/null >> make[1]: [local-distclean] Error 1 (ignored) >> rmdir texinfo/makeinfo texinfo/po texinfo/util 2>/dev/null >> make[1]: [local-distclean] Error 1 (ignored) >> rmdir fastjar gcc libiberty texinfo zlib 2>/dev/null >> make[1]: [local-distclean] Error 1 (ignored) >> find . -name config.cache -exec rm -f {} \; \; 2>/dev/null >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' >> >> >> >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdas6808 >> rm -f *.dep >> rm -f obj/m08pst.o obj/m08mch.o obj/m08adr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asstm8' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdas6808 >> rm -f *.dep >> rm -f obj/stm8pst.o obj/stm8mch.o obj/stm8adr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asstm8' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdas390 >> rm -f *.dep >> rm -f obj/ds8pst.o obj/ds8mch.o obj/ds8adr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8051' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdas8051 >> rm -f *.dep >> rm -f obj/i51pst.o obj/i51mch.o obj/i51adr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8051' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdasz80 >> rm -f *.dep >> rm -f obj/z80pst.o obj/z80mch.o obj/z80adr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' >> rm -f *core *[%~] *.[oa] >> rm -f .[a-z]*~ >> rm -f ../../bin/sdasrab >> rm -f *.dep >> rm -f obj/rabpst.o obj/rabmch.o obj/rabadr.o obj/asdbg.o obj/asdata.o >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o >> obj/dbuf.o >> obj/dbuf_string.o obj/.stamp >> if [ -d obj ]; then rmdir obj; fi >> rm -f Makefile >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' >> make[1]: *** No rule to make target `distclean'. Stop. >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' >> >> >> Maarten |
From: Molnár K. <car...@fr...> - 2016-05-02 18:46:29
|
> On Mon, 2 May 2016 19:39:38 +0200 (CEST) > "Maarten Brock" <sou...@ds...> wrote: > Karoly and others, > > I did not mean to say that your fix was wrong. Just that it did not fix > the problems that you seemed to claim that it fixed. Anyway, I'll have a > deeper look. > > I also just installed a new version of Ubuntu 16.04 LTS. This comes with a > much newer kernel (4.4) and newer tools like gcc 5.3.1. The problem I now > see is a segmentation fault in the host regression tests: > > gcc-torture-execute-20010403-1 (f: 0, t: 0, c: 1, b: 0, T: > 0) > Segmentation fault (core dumped) > (f: 0, t: 0, c: 0, b: 0, T: > 0) > gcc-torture-execute-20010422-1 (f: 0, t: 0, c: 1, b: 0, T: > 0) > > It's probably gcc-torture-execute-20010409-1 that fails here. N.B. It is > not noted in the summary! > I never saw this on my older Ubuntu 14.04 with 3.13 kernel and gcc 4.8.4. > > Maarten > Then this may be an error which depends on the gcc version. Károly > > On Wed, 20 Apr 2016 22:15:42 +0200 (CEST) > > "Maarten Brock" <sou...@ds...> wrote: > > > >> >> And then during make distclean: > >> >> > >> >> $ make distclean > /dev/null > >> >> make[3]: [distclean] Error 1 (ignored) > >> >> make[1]: [local-distclean] Error 1 (ignored) > >> >> make[1]: [local-distclean] Error 1 (ignored) > >> >> make[1]: [local-distclean] Error 1 (ignored) > >> >> make[1]: [local-distclean] Error 1 (ignored) > >> >> make[1]: *** No rule to make target `distclean'. Stop. > >> >> make[1]: *** No rule to make target `distclean'. Stop. > >> >> make[1]: *** No rule to make target `distclean'. Stop. > >> >> make[1]: *** No rule to make target `distclean'. Stop. > >> > > >> > This bug fixed in the [r9573] version. > >> > > >> > Karoly > >> > >> I hate to contradict you, but this really is not fixed. > >> > > > > I withdrew the faulty bugfix. > > > >> $ make distclean > /dev/null > >> make[3]: [distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: *** No rule to make target `distclean'. Stop. > >> > >> $ svn update > >> Updating '.': > >> At revision 9574. > >> > >> Here is the context where the errors occur: > >> > >> > >> make[3]: Entering directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> make[4]: Entering directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' > >> rm -f test-demangle > >> rm -f test-pexecute > >> rm -f test-expandargv > >> rm -f demangler-fuzzer > >> rm -f core > >> rm -f Makefile > >> make[4]: Leaving directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty/testsuite' > >> make SUBDIRS="" clean > >> make[4]: Entering directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> make SUBDIRS="" mostlyclean > >> make[5]: Entering directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> rm -rf *.o pic noasan core errs \#* *.E a.out > >> rm -f errors dummy config.h stamp-* > >> rm -f stamp-picdir stamp-noasandir > >> rm -f libiberty.aux libiberty.cp libiberty.cps libiberty.fn libiberty.ky > >> rm -f libiberty.log libiberty.tmp libiberty.tps libiberty.pg > >> rm -f libiberty.pgs libiberty.toc libiberty.tp libiberty.tpl > >> libiberty.vr > >> rm -f libtexi.stamp > >> make[5]: Leaving directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> rm -f *.a required-list tmpmulti.out > >> rm -f libiberty.dvi libiberty.pdf libiberty.info* libiberty.html > >> make[4]: Leaving directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> rm -f *~ Makefile config.cache config.status xhost-mkfrag TAGS > >> multilib.out > >> rm -f config.log > >> rmdir testsuite 2>/dev/null > >> make[3]: [distclean] Error 1 (ignored) > >> make[3]: Leaving directory > >> `/home/maarten/sdcc-pure/support/sdbinutils/libiberty' > >> > >> > >> > >> make[1]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' > >> make[2]: Entering directory `/home/maarten/sdcc-pure/support/sdbinutils' > >> make[2]: Nothing to be done for `distclean-target'. > >> make[2]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' > >> rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log > >> rm -f Makefile config.status config.cache mh-frag mt-frag > >> rm -f maybedep.tmp serdep.tmp > >> if [ "x86_64-unknown-linux-gnu" != "." ]; then \ > >> rm -rf x86_64-unknown-linux-gnu; \ > >> else true; fi > >> rm -rf build-x86_64-unknown-linux-gnu > >> if [ "." != "." ]; then \ > >> rm -rf .; \ > >> else true; fi > >> rm -f texinfo/po/Makefile texinfo/po/Makefile.in texinfo/info/Makefile > >> rm -f texinfo/doc/Makefile texinfo/po/POTFILES > >> rmdir texinfo/doc texinfo/info texinfo/intl texinfo/lib 2>/dev/null > >> make[1]: [local-distclean] Error 1 (ignored) > >> rmdir texinfo/makeinfo texinfo/po texinfo/util 2>/dev/null > >> make[1]: [local-distclean] Error 1 (ignored) > >> rmdir fastjar gcc libiberty texinfo zlib 2>/dev/null > >> make[1]: [local-distclean] Error 1 (ignored) > >> find . -name config.cache -exec rm -f {} \; \; 2>/dev/null > >> make[1]: [local-distclean] Error 1 (ignored) > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/support/sdbinutils' > >> > >> > >> > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdas6808 > >> rm -f *.dep > >> rm -f obj/m08pst.o obj/m08mch.o obj/m08adr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as6808' > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as6808' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asstm8' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdas6808 > >> rm -f *.dep > >> rm -f obj/stm8pst.o obj/stm8mch.o obj/stm8adr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asstm8' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdas390 > >> rm -f *.dep > >> rm -f obj/ds8pst.o obj/ds8mch.o obj/ds8adr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8xcxxx' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/as8051' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdas8051 > >> rm -f *.dep > >> rm -f obj/i51pst.o obj/i51mch.o obj/i51adr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/as8051' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdasz80 > >> rm -f *.dep > >> rm -f obj/z80pst.o obj/z80mch.o obj/z80adr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asz80' > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asz80' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' > >> rm -f *core *[%~] *.[oa] > >> rm -f .[a-z]*~ > >> rm -f ../../bin/sdasrab > >> rm -f *.dep > >> rm -f obj/rabpst.o obj/rabmch.o obj/rabadr.o obj/asdbg.o obj/asdata.o > >> obj/asexpr.o obj/aslex.o obj/aslist.o obj/asmain.o obj/asout.o > >> obj/assubr.o obj/assym.o obj/asmcro.o obj/sdas.o obj/strcmpi.o > >> obj/dbuf.o > >> obj/dbuf_string.o obj/.stamp > >> if [ -d obj ]; then rmdir obj; fi > >> rm -f Makefile > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' > >> make[1]: Entering directory `/home/maarten/sdcc-pure/sdas/asrab' > >> make[1]: *** No rule to make target `distclean'. Stop. > >> make[1]: Leaving directory `/home/maarten/sdcc-pure/sdas/asrab' > >> > >> > >> Maarten > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Maarten B. <sou...@ds...> - 2016-05-02 18:56:44
|
Hello again, > I also just installed a new version of Ubuntu 16.04 LTS. This comes with a > much newer kernel (4.4) and newer tools like gcc 5.3.1. The problem I now > see is a segmentation fault in the host regression tests: > > gcc-torture-execute-20010403-1 (f: 0, t: 0, c: 1, b: 0, T: > 0) > Segmentation fault (core dumped) > (f: 0, t: 0, c: 0, b: 0, T: > 0) > gcc-torture-execute-20010422-1 (f: 0, t: 0, c: 1, b: 0, T: > 0) > > It's probably gcc-torture-execute-20010409-1 that fails here. N.B. It is > not noted in the summary! > I never saw this on my older Ubuntu 14.04 with 3.13 kernel and gcc 4.8.4. Ok, this never failed for me because the test is not run for gcc < 5. But the test is also different from the original. Our test: A *bar (const char *v, int w, int x, const char *y, int z) { if (w) ASSERT (0); return 0; // Always return } void test (const char *x, int *y) { foo (d->a[d->b], "test", 200); d->a[d->b] = bar (x, b ? 0 : 65536, strlen (x), "test", 201); d->a[d->b]->a++; // This line gives segmentation fault because bar returns NULL if (y) d->a[d->b]->b = *y; } Original: A *bar (const char *v, int w, int x, const char *y, int z) { if (w) abort (); exit (0); // Never return } void test (const char *x, int *y) { foo (d->a[d->b], "test", 200); d->a[d->b] = bar (x, b ? 0 : 65536, strlen (x), "test", 201); d->a[d->b]->a++; // This line is NEVER executed if (y) d->a[d->b]->b = *y; } In other words, this test would fail on all targets if the simulator could catch a null pointer dereference. For mcs51-small this test could have overwritten the registers in regbank 0 if I had chosen to use 0 as idata identifier in generic pointers. Now it overwrites xdata. Since our testfwk.c still wants to print some stuff after __runSuite(), the closest solution would be use a longjmp(1) instead of the exit(0). Unfortunately not all targets have a working setjmp/longjmp yet. And further we should detect the missing Summary from each test. Maarten |
From: Philipp K. K. <pk...@sp...> - 2016-05-13 16:16:11
Attachments:
signature.asc
|
On 16.04.2016 20:44, Maarten Brock wrote: >> On 01.01.2016 17:54, Philipp Klaus Krause wrote: >>> SDCC seems quite stable currently, there were no recent big changes. >>> Since 3.5.0 we've seen the merge of current upstream binutils into our >>> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >>> management with lower overhead, and a lot of progress in >>> standard-compliance. >>> IMO, this would be a good time for a 3.6.0 release. >>> >>> Philipp >>> >> >> 2½ months have passed. And the list at >> >> http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List >> >> has become quite long. We have a lot of new features and important bug >> fixes since 3.5.0. >> >> Philipp > > I'm looking into the stability of SDCC. Currently make distclean fails: > > $ make distclean > /dev/null > make[3]: [distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > make[1]: [local-distclean] Error 1 (ignored) > […] These are not failures. In the Makefiles, there are commands prefixed with -, telling make to ignore the status code from the command (thus the (ignored) in the message). Thus whoever wrote that Makefile (it comes from binutils upstream) considered it ok for those --prefixed commands to fail. And indeed make does not stop there, but instead just happily continues. Philipp |
From: Maarten B. <sou...@ds...> - 2016-05-14 12:00:58
|
> On 16.04.2016 20:44, Maarten Brock wrote: >>> On 01.01.2016 17:54, Philipp Klaus Krause wrote: >>>> SDCC seems quite stable currently, there were no recent big changes. >>>> Since 3.5.0 we've seen the merge of current upstream binutils into our >>>> fork, bugfixes mostly for the stm8 and z80-related ports, new memory >>>> management with lower overhead, and a lot of progress in >>>> standard-compliance. >>>> IMO, this would be a good time for a 3.6.0 release. >>>> >>>> Philipp >>>> >>> >>> 2½ months have passed. And the list at >>> >>> http://sdcc.sourceforge.net/mediawiki/index.php/SDCC_3.6.0_Release#Feature_List >>> >>> has become quite long. We have a lot of new features and important bug >>> fixes since 3.5.0. >>> >>> Philipp >> >> I'm looking into the stability of SDCC. Currently make distclean fails: >> >> $ make distclean > /dev/null >> make[3]: [distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> make[1]: [local-distclean] Error 1 (ignored) >> [ ] > > These are not failures. In the Makefiles, there are commands prefixed > with -, telling make to ignore the status code from the command (thus > the (ignored) in the message). Thus whoever wrote that Makefile (it > comes from binutils upstream) considered it ok for those --prefixed > commands to fail. And indeed make does not stop there, but instead just > happily continues. > > Philipp Ok, so it seems. And I see them with binutils-gdb 2.26 as well. I still don't like them though. Is there no other way to handle cases like this? The lines say 'Error' which is totally misleading if it's only supposed to be an expected warning. Further it seemed to me sdbinutils left some files behind, that upstream binutils does not. But now I see those files are in their git as well, even though they are/can be (re)created by flex. I've put them in subversion as well (#9600). This also helps correct warnings generated by buggy flex versions. (e.g. flex 2.6.0 in Ubuntu 16.04) So what's left? make[1]: *** No rule to make target 'distclean'. Stop. make[1]: *** No rule to make target 'distclean'. Stop. make[1]: *** No rule to make target 'distclean'. Stop. make[1]: *** No rule to make target 'distclean'. Stop. And then there is this during make: Found a processor register! WREG Found a processor register! WREG Found a processor register! WREG Found a processor register! WREG Maarten |
From: Raphael N. <rn...@we...> - 2016-05-14 17:36:03
|
Hi, > Is there no other way to handle cases like this? > The lines say 'Error' which is totally misleading if it's only supposed to be an expected warning. One way to eliminate the warning / error with likely failing commands is to use command || true in the Makefile rule. Have a nice weekend, Raphael |