_Quad type

_Quad type

imagem de jjjforest

I am using Intel C++ compiler XE 13 with Visual Studio 2012 (or 2010).  I created a very simple console application (see attached file) to test the _Quad type using the compiler option "-Qoption,cpp,--extended_float_type".  The following is all the code.

int _tmain(int argc, _TCHAR* argv[])
{
    _Quad* p = new _Quad[1];
    p[0] = 1.1;
    delete []p;
    return 0;
}

When I run the application in release mode (without using debugger), the program crashes (although it may not crash on the first try, but on the thrid or fourth try).  Can anybody repeat this behavior?  The crash does not happen if I use stack memory instead of free store.

Thanks,

AnexoTamanho
Download quadtest.zip7.49 KB
8 posts / 0 new
Último post
Para obter mais informações sobre otimizações de compiladores, consulte Aviso sobre otimizações.
imagem de Casey

I built your (slightly modified) testcase with icpc 14.0 on Linux.  No segfaults, cannot reproduce behavior.

imagem de jjjforest

Thanks, Casey.  I am using Visual Studio 2012 and 2010 on Windows 8, with Intel C++ XE 13 evaluation version.  The crash happens on consistently on release mode for this simplest code.

imagem de jjjforest

This is been confirmed by Intel Support that it is a bug.  The following code works for 64-bit application but not for 32-bit application on Windows.  It is a real suprise to me.

   _Quad* p = new _Quad[1];
    p[0] = 1.1;

imagem de iliyapolak

Ca you post the disassembly?

 

imagem de jjjforest

Here is the debug exe (rename quadTest.txt to quadTest.exe) as well as the source code for Visual Studio 2012.  It crashes in debug mode (run without debugging).  A Intel support person can reproduce this bug.  It seems the bug happens in 32-bit app, not 64-bit app.

Anexos: 

AnexoTamanho
Download quadtest.txt474 KB
Download quadtest.zip7.27 KB
Download crash.png20.5 KB
imagem de Judith Ward (Intel)

 

I can reproduce this with our latest development compiler. i have entered this in our internal bug tracking database as DPD200248294. Thank you for reporting this.

imagem de jjjforest

I think Intel should put a hot fix soon as this is such a basic stuff for a compiler.

Faça login para deixar um comentário.