https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #12 from Julian Seward <jsew...@acm.org> --- (In reply to Ivo Raisr from comment #11) > 5904a71c b p_CmpNEZ32_Or32.5344 > 5904a720 b p_CmpNEZ32_And32.5340 > 5904a724 b p_zwiden_load64.5765 > 5904a728 b p_CmpwNEZ64_Or64.5612 > 5904a72c B vex_control <=== > 5904a748 B vex_traceflags > 5904a74c B vex_debuglevel > 5904a750 B vex_log_bytes > 5904a754 B vex_failure_exit > 5904a758 B vex_initdone I don't know. That all looks pretty harmless. The p_* values are single pointers to IR trees used in insn selection (they are templates used for matching) and I can't imagine how they could be involved in an array overrun. I do notice that iropt_verbosity is the first word of VexControl, but whether that is significant, I also don't know. -- You are receiving this mail because: You are watching all bug changes.
