Skip to content

cpu/native: use correct isr_stack for valgrind #21492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

OlegHahm
Copy link
Member

@OlegHahm OlegHahm commented May 16, 2025

Contribution description

In the cleanup PR for native (#21283) (90a3f3f) the ISR stack variable got renamed from __isr_stack to _isr_stack but the valgrind configuration hasn't been updated.

Testing procedure

Build any application for native with make all-valgrind.

Issues/PRs references

Fixes a leftover issue from #21283

@github-actions github-actions bot added Platform: native Platform: This PR/issue effects the native platform Area: cpu Area: CPU/MCU ports labels May 16, 2025
@crasbe crasbe added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels May 16, 2025
@crasbe
Copy link
Contributor

crasbe commented May 16, 2025

Small nitpick: The title and commit message should be cpu/native instead of cpu: native:.

Otherwise I just wonder how we could ensure that this would caught by CI in the future (but that's not really part of this PR).

@riot-ci
Copy link

riot-ci commented May 16, 2025

Murdock results

✔️ PASSED

af6da34 cpu/native: use correct isr_stack for valgrind

Success Failures Total Runtime
10346 0 10346 10m:28s

Artifacts

@OlegHahm
Copy link
Member Author

Totally fine with changing this but do we have well-defined rules for that? But indeed there seems to be a preference toward the proposed format:

> git log --oneline | grep -c "cpu: native:"
19
> git log --oneline | grep -c "cpu/native:" 
145

But some people seem to prefer native: only:

> git log --oneline | grep -cE "[[:xdigit:]]{10} native:"
139

@crasbe
Copy link
Contributor

crasbe commented May 16, 2025

Totally fine with changing this but do we have well-defined rules for that?

Indeed, there is the commit convention: https://github.com/RIOT-OS/RIOT/blob/master/CONTRIBUTING.md#commit-conventions

It seems like we can blame Kaspar mostly for the exceptions 🤣

cbuec@W11nMate:~/RIOTstuff/riot-gettingstarted/RIOT$ git log --pretty=format:"%an, %s%n" | grep "cpu: native:"
Oleg Hahm, cpu: native: use correct isr_stack for valgrind
Kaspar Schleiser, cpu: native: uart: adapt to changed DEBUG
Kaspar Schleiser, cpu: native: always select periph_uart
Kaspar Schleiser, cpu: native: reorganize Makefile.features
Martine Lenders, cpu: native: make syscalls vfs ready (introduce real_fcntl)
Kaspar Schleiser, cpu: native: add vfs wrappers
Kaspar Schleiser, cpu: native: fix thread_yield_higher inisr() case
Kaspar Schleiser, cpu: native: use gnu99 C dialect
Iván Briano, cpu: native: Add [v]fprintf to syscalls
Kaspar Schleiser, cpu: native: make netdev2_tap internal functions static
Kaspar Schleiser, cpu: native: netdev2_tap: don't pass isr_arg on rx complete event
Kaspar Schleiser, cpu: native: adapt xtimer backoff values to periph/timer change
Kaspar Schleiser, cpu: native: netdev2_tap: make use of netdev2_eth module
Kaspar Schleiser, cpu: native: remove hwtimer traces
Kaspar Schleiser, cpu: native: minor timer-related doxygen updates
Kaspar Schleiser, cpu: native: remove hwtimer_compat dependency
Benoît Canet, cpu: native: switch to hwtimer_compat
Kaspar Schleiser, cpu: native: work around shared errno in _native_lpm_sleep
Kaspar Schleiser, cpu: native: add tap implementation of dev_eth (ng_nativenet)

In 90a3f3f the ISR stack variable got
renamed from __isr_stack to _isr_stack but the valgrind configuration
hasn't been updated.
@OlegHahm OlegHahm force-pushed the pr/native/adjust_isr_stack_for_valgrind branch from 220ea10 to af6da34 Compare May 16, 2025 10:24
@OlegHahm OlegHahm changed the title cpu: native: use correct isr_stack for valgrind cpu/native: use correct isr_stack for valgrind May 16, 2025
@OlegHahm
Copy link
Member Author

To be honest this looks to me rather like an example than a rule. So, if we want to streamline this, we should be probably more specific in that document. Question here is: do you see an advantage of being more pedantic here?

@crasbe crasbe enabled auto-merge May 16, 2025 12:37
@crasbe crasbe disabled auto-merge May 16, 2025 12:39
@crasbe crasbe enabled auto-merge May 16, 2025 12:40
@crasbe crasbe added this pull request to the merge queue May 16, 2025
@crasbe
Copy link
Contributor

crasbe commented May 16, 2025

To be honest this looks to me rather like an example than a rule. So, if we want to streamline this, we should be probably more specific in that document. Question here is: do you see an advantage of being more pedantic here?

I do believe that it makes sense to keep the commit messages uniform. Of course there are exceptions, but sometimes something slips through of course and there might be some stuff from "back in the day" as well.

Maybe that discussion should be outsourced to an Issue or the Matrix chat though.

Merged via the queue into RIOT-OS:master with commit 2831a7f May 16, 2025
26 checks passed
@OlegHahm OlegHahm deleted the pr/native/adjust_isr_stack_for_valgrind branch May 16, 2025 19:34
@Teufelchen1 Teufelchen1 added this to the Release 2025.07 milestone Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: cpu Area: CPU/MCU ports CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Platform: native Platform: This PR/issue effects the native platform Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants