Petro Karashchenko

Also code: ``` typedef volatile struct { uint32_t a0[2]; } __attribute__((packed,uncached)) pu_st1; int my_func2(uint32_t p0, uint32_t p1); int my_func1(pu_st1 *p) { return my_func2(p->a0[0], p->a0[1]); } ``` and code ``` typedef...

@claziss I was able to narrow down the issue to a single line. It is located in `gcc/emit-rtl.c` file in `adjust_address_1` method. `packed` attribute types member access is expanded into...

@claziss is there any chance to get this issue fixed in `2020.09` release? Meanwhile, I've done some communication with the community trying to discuss the point that I found in...

Some how yes. But in code the need to track all variables with uncached access gets risen. I mean if I `typedef volatile __attribute__((uncached)) int uncached_int;`, then in all places...

I mean it will be good to have an option so `section` attribute to be added implicitly for all variables that are declared with `uncached` attribute. Similar to MetaWare compiler...

It is just an idea. I just thought about `-fdata-sections`, so `.ucdata.` or `.ucbss.` can be appended. But I do not fully understand the effort that is needed to get...