Skip to content
New issue

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

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

Already on GitHub? # to your account

debug option provided by gcc10: -fanalyzer #7561

Open
d-a-v opened this issue Aug 29, 2020 · 1 comment
Open

debug option provided by gcc10: -fanalyzer #7561

d-a-v opened this issue Aug 29, 2020 · 1 comment

Comments

@d-a-v
Copy link
Collaborator

d-a-v commented Aug 29, 2020

-fanalyzer option is useful and currently gives insights on code in master.
Compilation is however slower when using it.
Should we add a new enable option in the generic board menus ?
Or a debug option (that would be available for all boards) ?

related: new option -Wstack-usage= described in #7398

@earlephilhower
Copy link
Collaborator

My thought is "yes" for stack-usage, but "no" for -fanalyzer.

The reason is that in my experience fanalyzer gets confused a lot, both in the core and in the libs, and you end up with way more junk dumps than is reasonable. It also isn't clean on the core, so unless we mop up the ~30 spots it doesn't like then any user code catches would be hidden in that.

Stack-usage is a pretty simple and clean check, though, and only complains in 3-4 spots that we can (should) easily fix.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants