Debug messages printed when using treedec in SDCC

[spth]

When compiling the regression test gcc-torture-execute-pr77766 with current SDCC, the following debug output is seen:

incomplete /usr/local/include/treedec/degree.hpp:190:unlink unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove incomplete /usr/local/include/treedec/degree.hpp:190:unlink unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove incomplete /usr/local/include/treedec/degree.hpp:190:unlink unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove

This happens for the current version from the develop branch.

To reproduce: Install treedec from git, compile sdcc from svn, run "make test-stm8" in sdcc/support/regression.

Philipp

[felix-salfelder]

On Wed, Mar 14, 2018 at 02:05:43AM -0700, Philipp Klaus Krause wrote:

When compiling the regression test gcc-torture-execute-pr77766 with current SDCC, the following debug output is seen:

incomplete /usr/local/include/treedec/degree.hpp:190:unlink unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove unreachable /usr/local/include/treedec/bucket_sorter.hpp:72:remove [..]

reproduced.

is there a way to run (just) gcc-torture-execute-pr77766?

thanks felix

[spth]

Once you run the tests, another "make test-stm8" will just run the ones that changed, i.e. "touch tests/gcc-torture-execute-pr77766.c" && make test-stm8" will do. Alternatively, you can comment out the .SILENT in the Makefile to see the actual sdcc invokation with parmaters, and use that one.

Philipp

[felix-salfelder]

On Wed, Mar 14, 2018 at 09:28:47AM -0700, Philipp Klaus Krause wrote:

Once you run the tests, another "make test-stm8" will just run the ones that changed, i.e. "touch tests/gcc-torture-execute-pr77766.c" && make test-stm8" will do. Alternatively, you can comment out the .SILENT in the Makefile to see the actual sdcc invokation with parmaters, and use that one.

thanks.

i get

$ make test-stm8 [..] unreachable etc... [..] switch (f: 0, t: 216, c: 36, b: 29316, T: 52408) uminus (f: 0, t: 72, c: 36, b: 33313, T: 108125) using (f: 0, t: 0, c: 3, b: 2008, T: 6126) vaargs (f: 0, t: 64, c: 8, b: 14864, T: 22032) gen/stm8/version/version.c:10: syntax error: token -> ';' ; column 25 /home/felix/extern/sdcc/support/regression/ports/stm8/spec.mk:54: recipe for target 'gen/stm8/version/version.rel' failed make[3]: [gen/stm8/version/version.rel] Error 1 Makefile:290: recipe for target 'results/stm8/version.out' failed make[2]: [results/stm8/version.out] Error 2 Makefile:309: recipe for target 'test-port' failed make[1]: [test-port] Error 2 Makefile:181: recipe for target 'test-stm8' failed make: [test-stm8] Error 2

and subsequently

$ make test-stm8 Running stm8 regression tests gen/stm8/version/version.c:10: syntax error: token -> ';' ; column 25 /home/felix/extern/sdcc/support/regression/ports/stm8/spec.mk:54: recipe for target 'gen/stm8/version/version.rel' failed make[3]: [gen/stm8/version/version.rel] Error 1 Makefile:290: recipe for target 'results/stm8/version.out' failed make[2]: [results/stm8/version.out] Error 2 Makefile:309: recipe for target 'test-port' failed make[1]: [test-port] Error 2 Makefile:181: recipe for target 'test-stm8' failed make: [test-stm8] Error 2

make clean allows me to get back to start.

i'll try .SILENT.

cheers felix

[spth]

As a quick workaround for the failure in version.c you could just delete tests/version.c locally. I guess you got sdcc via git-svn or so and this causes the issue in version.c.

Philipp

[felix-salfelder]

On Thu, Mar 15, 2018 at 03:25:35AM -0700, Philipp Klaus Krause wrote:

As a quick workaround for the failure in version.c you could just delete tests/version.c locally. I guess you got sdcc via git-svn or so and this causes the issue in version.c.

got it somehow. thanks.

i have ported the issue to a tdlib unit test. in the process of debugging..

[felix-salfelder]

it should be fixed in develop, together with 2 other bugs.

please confirm and/or close the bug.

[spth]

Thanks.

Philipp