|
Ran
|
Jobs
1
|
Files
244
|
Run time
26s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/micropython/micropython/commit/<a class=hub.com/micropython/micropython/commit/<a class="double-link" href="https://git"><a class=hub.com/micropython/micropython/commit/fd49fcb229b6694d69d8f7646c7940e40b67a0cb">fd49fcb22<a href="https://github.com/micropython/micropython/commit/fd49fcb229b6694d69d8f7646c7940e40b67a0cb"><a href="https://github.com/micropython/micropython/commit/fd49fcb229b6694d69d8f7646c7940e40b67a0cb">&quot;&gt;stm32/gccollect: Always use MP_STATE_THREAD(stack_top) to get stack top. In a non-thread build, using &amp;_ram_end as the top-of-stack is no longer correct because the stack is not always at the very top end of RAM. See eg </a><a class="double-link" href="https://github.com/micropython/micropython/commit/<a class="double-link" href="https://github.com/micropython/micropython/commit/04c7cdb668cc7ee391ef5fe000f825389197f7e2">04c7cdb66</a>">04c7cdb66</a><a href="https://github.com/micropython/micropython/commit/fd49fcb229b6694d69d8f7646c7940e40b67a0cb"> and </a><a class="double-link" href="https://github.com/micropython/micropython/commit/<a class="double-link" href="https://github.com/micropython/micropython/commit/378659209778a1bde24e9b15793087023b02bbd9">378659209</a>">378659209</a><a href="https://github.com/micropython/micropython/commit/fd49fcb229b6694d69d8f7646c7940e40b67a0cb">. The correct value to use is &_estack, which is the value stored in MP_STATE_THREAD(stack_top), and using the same code for both thread and non-thread builds makes the code cleaner.
18448 of 18825 relevant lines covered (98.0%)
365028.72 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 3 | 10936.3 (NAME="unix coverage build and tests") | 0 |
98.0 |
Travis Job 10936.3 |