[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 345753] New: OS X: sanityCheckFail: exiting due to bad IR for Iop_AddF64
From:       <rhyskidd () gmail ! com>
Date:       2015-04-01 11:25:03
Message-ID: bug-345753-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=345753

            Bug ID: 345753
           Summary: OS X: sanityCheckFail: exiting due to bad IR for
                    Iop_AddF64
           Product: valgrind
           Version: 3.10 SVN
          Platform: Mac OS X Disk Images
                OS: OS X
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: vex
          Assignee: jseward@acm.org
          Reporter: rhyskidd@gmail.com

Running through the regression tests on OS X (10.9 here, using clang based on
LLVM 3.5svn) I see the following interesting failures in the backend of
memcheck/tests/vbit-test/vbit-test.

I'm not sure how prevalent this issue is cascading through other code, but it
looks pretty serious on this platform. This regression test also fails on OS X
10.10.

$ valgrind -q ./memcheck/tests/vbit-test/vbit-test -v -v
Testing operator Iop_Add8
Testing operator Iop_Add16
...
Testing operator Iop_1Sto64
Testing operator Iop_AddF64
 op name: AddF64
 op type is (I32,F64,F64) -> F64
arg tys are (I32,D32,D32)

IR SANITY CHECK FAILURE

IRSB {

   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   IR-NoOp
   ------ IMark(0x8450, 19, 0) ------
   STle(0x100034A70:I64) =
AddF64(0x0:I32,LDle:D32(0x100034AC0:I64),LDle:D32(0x100034B10:I64))
   PUT(872) = 0x100008450:I64
   PUT(880) = 0x13:I64
   PUT(184) = 0x100008463:I64
   PUT(184) = GET:I64(184); exit-InvalICache
}

IN STATEMENT:

STle(0x100034A70:I64) =
AddF64(0x0:I32,LDle:D32(0x100034AC0:I64),LDle:D32(0x100034B10:I64))

ERROR = Iex.Triop: arg tys don't match op tys
... additional details precede BB printout



vex: the `impossible' happened:
   sanityCheckFail: exiting due to bad IR
vex storage: T total 769677136 bytes allocated
vex storage: P total 640 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==22591==    at 0x23804E12E: ???
==22591==    by 0x23804E54C: ???
==22591==    by 0x23804E5EF: ???
==22591==    by 0x23804E592: ???
==22591==    by 0x23804E5FA: ???
==22591==    by 0x23806E994: ???
==22591==    by 0x238111390: ???
==22591==    by 0x23811D010: ???
==22591==    by 0x23811DE4E: ???
==22591==    by 0x23811C4C8: ???
==22591==    by 0x23810F1AD: ???
==22591==    by 0x23806E73B: ???
==22591==    by 0x2380D9320: ???
==22591==    by 0x2380D7436: ???
==22591==    by 0x2380E9841: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==22591==    at 0x100008450: valgrind_execute_test (in
./memcheck/tests/vbit-test/vbit-test)
==22591==    by 0x100001EB9: test_binary_op (in
./memcheck/tests/vbit-test/vbit-test)
==22591==    by 0x100000C6F: main (in ./memcheck/tests/vbit-test/vbit-test)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

Reproducible: Always

Steps to Reproduce:
1. make regtest
2. $ perl tests/vg_regtest memcheck/tests/vbit-test/vbit-test
OR
3. $ valgrind -q ./memcheck/tests/vbit-test/vbit-test -v -v



$ clang -v
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix
$ uname -mrs
Darwin 13.4.0 x86_64

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]