Unable to get examples successfully built on Visual Studio 2012/Win7 platform

233 views
Skip to first unread message

mg

unread,
Nov 22, 2012, 4:43:50 AM11/22/12
to ispc-...@googlegroups.com
Hi,

  I am trying to build ispc examples using Visual Studio 2012, which fails with an error when building the simple.cpp file

    C:\soft\ispc-v1.3.0-windows\examples\x64\Release\simple_ispc.h : fatal error LNK1107: invalid or corrupt file: cannot read at 0x405

ispc -O2 --arch=x86-64 --target=avx simple.ispc -o simple_ispc.o -h simple_ispc.h

Thanks

mg

Dmitry Babokin

unread,
May 13, 2013, 3:10:28 AM5/13/13
to ispc-...@googlegroups.com
I'm not sure that I got you right. But the problems with COFF and
compiler fail during "whole program optimization" at link step are
known VS problems, which are not related to ISPC. If you install
VS2012 on your computer and still using VS2010 (i.e. not upgrading the
project causes using VS2010 toolchain), make sure that you install
VS2010 SP1 after that. It's also recommended to use VS2012 Update2 due
to know bugs in VS2012 which trigger on LLVM build (bugs are
correctness bugs, which supposed to show off on LLVM test suit).

Check MSDN for more details of COFF bug.

On Mon, May 13, 2013 at 12:38 AM, <mharv...@gmail.com> wrote:
> all built but one by;
>
> not updated to vs2012 when prompted upon loading solution. tried with and
> without and with failed coff error which is probably more indicative of the
> problem than the original reading past end of file error. I think you'll
> find that 0x405 is one more than you file length.
>
> set linker to no incremental linking for each project and success
>
> mh
>
> --
> You received this message because you are subscribed to the Google Groups
> "Intel SPMD Program Compiler Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ispc-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Abdulla Hammad

unread,
Jan 12, 2015, 4:55:49 PM1/12/15
to ispc-...@googlegroups.com
I think this problem has been solved here. I have tried the fix MS suggested and it is working.
Reply all
Reply to author
Forward
0 new messages