[Bug target/25176] FAIL: Array_3 -O3 execution - bytecode-native test

2005-12-01 Thread christian dot joensson at gmail dot com
--- Comment #4 from christian dot joensson at gmail dot com 2005-12-01 10:06 --- Not 100% sure, but I do believe this has happend on sparc/sparc64 linux for a quite some time... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25176

[Bug target/25176] FAIL: Array_3 -O3 execution - bytecode-native test

2005-11-30 Thread amodra at bigpond dot net dot au
--- Comment #2 from amodra at bigpond dot net dot au 2005-11-30 13:07 --- I had a little play at implementing unwinder info for the epilogue. It's easy to arrange for a DW_CFA_def_cfa_offset: 0 to be emitted on the stack restore. However, often the function exit isn't emitted last.

[Bug target/25176] FAIL: Array_3 -O3 execution - bytecode-native test

2005-11-30 Thread rth at gcc dot gnu dot org
--- Comment #3 from rth at gcc dot gnu dot org 2005-11-30 23:07 --- Fixing the unwinder to handle epilogues is harder than you think, I think. My guess is that it'll require completely rewriting the unwind generator. It'll need to be CFG aware, which means it'll have to happen while the

[Bug target/25176] FAIL: Array_3 -O3 execution - bytecode-native test

2005-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-30 02:26 --- Confirmed, also happens on ppc-darwin. (Note this is most likely on other targets too, there is a bug about x86_64 and this IIRC to get libuwind to pass its tests). -- pinskia at gcc dot gnu dot org changed: