[Bug target/89251] [2018-q4m] Wrong datatype optimization on bitfield

2019-02-08 Thread david.koch at libertysurf dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89251 --- Comment #5 from Kochise --- "The pointer I access is volatile, not the uint32_t behind" Understand this : ((volatile MyRegDef*) ADDR)->enable; <- TYPO in the original message I couldn't edit Not this : typedef union MyRegDef { struct

[Bug target/89251] [2018-q4m] Wrong datatype optimization on bitfield

2019-02-08 Thread david.koch at libertysurf dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89251 --- Comment #4 from Kochise --- The pointer I access is volatile, not the uint32_t behind. Why would I ? The 'volatile' keyword has no meaning to change the data size being processed, only removing the caching behavior of the compiler. If the co

[Bug target/89251] [2018-q4m] Wrong datatype optimization on bitfield

2019-02-08 Thread david.koch at libertysurf dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89251 --- Comment #2 from Kochise --- You really considered to tag this issue as RESOLVED INVALID with this "trick" ? I showed you that just stuffing the uint32_t with unused bits change the behavior, this is clearly a bug. You cannot be serious. Come

[Bug c++/89251] New: [2018-q4m] Wrong datatype optimization on bitfield

2019-02-08 Thread david.koch at libertysurf dot fr
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: david.koch at libertysurf dot fr Target Milestone: --- (probably related to #83784) The setting : STM32L476 / Cortex-M4 GCC 8.2.1 from ARM (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads) 1