Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpoulhies at kalray dot eu
Target Milestone: ---
The following code has different executions in O0 and O3.
It looks like GCC is able to optimize the `throw s` in `test()` by calling
`terminate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67282
Marc POULHIÈS changed:
What|Removed |Added
CC||mpoulhies at kalray dot eu
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95741
--- Comment #3 from Marc POULHIÈS ---
Yes you are right, sorry. Mistake caused by previous change in the title...
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mpoulhies at kalray dot eu
Target Milestone: ---
Giving this to all GCC on godbolt.org (9.2 to 4.1.2) :
#include
int main (int argc, char **argv) {
struct S {
char toto[argc];
};
int f (struct S arg
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: mpoulhies at kalray dot eu
Target Milestone: ---
The following code is miscompiled in O2 only (0,1 and 3 are correct):
typedef unsigned long long uint64_t;
uint64_t data_array[16] = {0};
unsigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91616
--- Comment #3 from Marc POULHIÈS ---
Ok, sorry for the incorrect report.
The problem was found in our port of GCC where the code actually really
accesses an incorrect memory location and seeing this very large offset added
to data array lead me
Assignee: unassigned at gcc dot gnu.org
Reporter: mpoulhies at kalray dot eu
Target Milestone: ---
Since r217769, a target without support for static chain will not work.
Previous this change, the message
```
nested functions not supported on this target
```
was displayed only when
