LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Compiler crash (in Debug build): "Instruction does not dominate all uses!"

CVI 2015 crashes with following errors:

Build Status (crash.prj - Debug)
 emf.c - 19 warnings
      [...warnings cut...]
      1, 1   Instruction does not dominate all uses!
      1, 1   %13298 = call %3* @_PtrCastToScalar(%3* inttoptr (i32 3 to %3*), { i8*, i32 }* %827, i32 2), !dbg !2461
      1, 1   %13745 = call %3* @_PtrCastToScalar(%3* %13298, { i8*, i32 }* %827, i32 2), !dbg !2533
      1, 1   Instruction does not dominate all uses!
      1, 1   %13745 = call %3* @_PtrCastToScalar(%3* %13298, { i8*, i32 }* %827, i32 2), !dbg !2533
      1, 1   %14123 = call %3* @_PtrCastToScalar(%3* %13745, { i8*, i32 }* %827, i32 2), !dbg !2594
      1, 1   Instruction does not dominate all uses!
      1, 1   %14123 = call %3* @_PtrCastToScalar(%3* %13745, { i8*, i32 }* %827, i32 2), !dbg !2594
      1, 1   %14719 = call %3* @_PtrCastToScalar(%3* %14123, { i8*, i32 }* %827, i32 2), !dbg !2685
      1, 1   Instruction does not dominate all uses!
      1, 1   %14719 = call %3* @_PtrCastToScalar(%3* %14123, { i8*, i32 }* %827, i32 2), !dbg !2685
      1, 1   %15178 = call %3* @_PtrCastToScalar(%3* %14719, { i8*, i32 }* %827, i32 2), !dbg !2757
      1, 1   Broken module found, compilation aborted!
      1, 1   This application has requested the Runtime to terminate it in an unusual way.
      1, 1   Please contact the application's support team for more information.
Build failed.

Steps to reproduce:

  1. Download zint-2.6.1.src.tar.gz from https://sourceforge.net/projects/zint/files/zint/2.6.1/
  2. Copy emf.c, emf.h, common.h, zint.h from backend dir into an empty dir
  3. Create empty textfile malloc.h
  4. Create new CVI project
  5. Add emf.c and add "." to include paths
  6. Compile emf.c

Build succedes when using Release mode.

-----------------------
/* Nothing past this point should fail if the code is working as intended */
0 Kudos
Message 1 of 3
(2,816 Views)

The last time I had an issue like this and no forum topics reflecting my issue, I reinstalled CVI. The root cause of the issue was never running a test install from a much older version of CVI that rewrote path variables and overwriting newer dll's.

 

 

Jattie van der Linde
Engineering Manager, Software & Automation
TEL Magnetic Solutions Ltd
0 Kudos
Message 2 of 3
(2,790 Views)

I tried it in a clean VM. It happens there, too.

-----------------------
/* Nothing past this point should fail if the code is working as intended */
0 Kudos
Message 3 of 3
(2,723 Views)