Skip to content

Conversation

@VynDragon
Copy link
Contributor

Maybe the last time? associated issue outlines details

Maybe the last time? associated issue outlines details

Signed-off-by: Camille BAUD <[email protected]>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 9, 2026

Copy link
Contributor

@josuah josuah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still puzzled to see this driver being affected by the compiler reordering everything.

Maybe there is some other bug somewhere, I remember you saying the disassembly was shuffling things a lot and that volatile everything was not a complete fix. But it could also be a compiler design choice or plain bug, so if this is possible to fix it at the driver level in the meantime it's good IMHO.

Context is, IIRC Zephyr SDK 0.17.4.

@hamoodmohameed16-source

Maybe the last time? associated issue outlines details

Still puzzled to see this driver being affected by the compiler reordering everything.

Maybe there is some other bug somewhere, I remember you saying the disassembly was shuffling things a lot and that volatile everything was not a complete fix. But it could also be a compiler design choice or plain bug, so if this is possible to fix it at the driver level in the meantime it's good IMHO.

Context is, IIRC Zephyr SDK 0.17.4.

@hamoodmohameed16-source

[ ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Recurrent compiler optimization related failure of BFLB I2C driver

5 participants