zephyrproject-rtos / zephyr

Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
https://docs.zephyrproject.org
Apache License 2.0
10.88k stars 6.63k forks source link

qemu_cortex_a53_smp board can not support `CONFIG_NO_OPTIMIZATIONS=y` config. #76362

Closed cocoeoli closed 1 month ago

cocoeoli commented 3 months ago

Describe the bug When I enable the 'CONFIG_NO_OPTIMIZATIONS=y' option and run sample/synchronization, it can not work well(Just print two line and no ohter message): image

To Reproduce

  1. Adding 'CONFIG_NO_OPTIMIZATIONS=y' to 'qemu_cortex_a53_qemu_cortex_a53_smp_defconfig';
  2. west build -b qemu_cortex_a53_smp samples/synchronization/
  3. west build -t run
  4. See bug;

Environment (please complete the following information):

thedjnK commented 3 months ago

Did you increase the stack sizes?

cocoeoli commented 3 months ago

Did you increase the stack sizes?

No, the stack size is default value(4096). I try to increase it, but it still not wrok.

jhedberg commented 3 months ago

Did you increase the stack sizes?

No, the stack size is default value(4096). I try to increase it, but it still not wrok.

Which stack did you increase? There are probably several thread stacks that may need modification (e.g. system work queue, main, interrupt, etc)

cfriedt commented 3 months ago

@cocoeoli - have you tried debugging with gdb? It would be great if you could help pinpoint where the issue is. E.g. by providing a stack trace

jhedberg commented 3 months ago

In general, these stack size increase situations when disabling optimizations is something that we can't (and won't) fix upstream for all cases.

cocoeoli commented 3 months ago

Did you increase the stack sizes?

No, the stack size is default value(4096). I try to increase it, but it still not wrok.

Which stack did you increase? There are probably several thread stacks that may need modification (e.g. system work queue, main, interrupt, etc)

The stack size I increased are below: image

cocoeoli commented 3 months ago

@cocoeoli - have you tried debugging with gdb? It would be great if you could help pinpoint where the issue is. E.g. by providing a stack trace

I am trying to debug.

cocoeoli commented 3 months ago

In general, these stack size increase situations when disabling optimizations is something that we can't (and won't) fix upstream for all cases.

Yes, I think some use cases may require disabling optimizations.

github-actions[bot] commented 1 month ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.