internal error assertion failed

internal error assertion failed

Portrait de pivo12

Sirs,

I know the '/v' is not a valid compiler option, but when I try to use it, I got the following error messages:

icl /v

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 13.1.3.198 Build 20130607
Copyright (C) 1985-2013 Intel Corporation. All rights reserved.
icl: command line warning #10006: ignoring unknown option '/v'

icl: internal error: Assertion failed (shared/driver/driver.c, line 370)

--------------------------------------------------------
Windows 7 64 bit Home Premium
Intel i5-2400 CPU

Steven T.

 

 

 

 

 

 

14 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.
Portrait de Jennifer J. (Intel)

Thanks for reporting this issue!

I checked with 13.0 update5, it does have this issue. But with the 14.0 beta update it works fine. We will be only fixing high bugs for 13.x now, so I will not file any ticket for this one against 13.x.

thanks,
Jennifer

Portrait de Sergey Kostrov

>>...icl: internal error: Assertion failed (shared/driver/driver.c, line 370)

I did a quick verification with version 12 and I confirm that the problem is version 13 specific.

..\Composer XE 2011 SP1>icl.exe /v
Intel(R) C++ Compiler XE for applications running on IA-32, Version 12.1.7.371 Build 20120928
Copyright (C) 1985-2012 Intel Corporation. All rights reserved.
icl: command line warning #10006: ignoring unknown option '/v'

icl: command line error: no files specified; for help type "icl /help"

..\Composer XE 2011 SP1>icl.exe -v
Intel(R) C++ Compiler XE for applications running on IA-32, Version 12.1.7.371 Build 20120928
Copyright (C) 1985-2012 Intel Corporation. All rights reserved.
icl: command line warning #10006: ignoring unknown option '/v'

icl: command line error: no files specified; for help type "icl /help"

I didn't have any 'Assertion failed' messages.

Portrait de Stephane L.

Under a Linux-like environment for Windows, most of program need the usual configure, make, make install to get it running. Using Intel(R) C++ Intel(R) 64 Compiler XE 2013 under cygwin, I am trying to compile a program by first doing

./configure

I got the following error message : checking whether the C compiler works ... no
                                                   configure: error: C compiler cannot create executables
                                                   See 'config.log' for more details

Of course, looking at config.log, the error message is the same as Steven T.: 

icl: command line warning #10006: ignoring unknown option '/-version'
icl: internal error: Assertion failed <shared/driver/driver.c, line 370>

So although it is a minor error, I cannot compile some programs that need to check the version of my C compiler during the configure process. Is there a simple way to fix this problem instead of waiting the 14.0 version ? 

Thank you,

Stephane L.

Portrait de Sergey Kostrov

Stephane, Thanks for the information. If you really want to see the issue is resolved create a complete test-case ( with all additional files, etc / I mean configuration files ) and upload it.

Portrait de Stephane L.

Thank you !

Portrait de Casey

Sergey,

   This is the test case the autoconf tools use for "checking for C compiler version" :

$CC --version

Where $CC is the compiler command (e.g. icc, icl, gcc) and in Stephane's case on windows it is using /-version rather than --version.

   This is the test case the autoconf tools use for the "checking whether the C compiler works"

 int
 main ()
 {
 ;
 return 0;
 }

As per the OP, the testcase that is causing Stephane's autoconf to fail is likely the invocation of "icl /-version", which is your minimal reproducer testcase.

Portrait de Sergey Kostrov

>>int
>>main ()
>>{
>>;
>>return 0;
>>}

Thanks, Casey. Did you put ; in the main function accidently or it is just the typo?

Portrait de Casey

No typo.  It looks a bit odd, but that is what autotools uses to test that the C compiler can produce executables.

Portrait de Stephane L.

After looking carefully the config.log file, it seems that the problem does not come from the command "-v'. Here is the config.log file output (using intel composer xe 2013 14.0 Beta):

## ----------- ##

## Core tests. ##

## ----------- ##

configure:5143: checking for C compiler version

configure:5152: icl --version >&5

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.\

0.068 Beta Build 20130529

Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

icl: command line warning #10006: ignoring unknown option '/-version'

icl: NOTE: The Beta evaluation period for this product ends on 27-sep-2013 UTC.

icl: command line error: no files specified; for help type "icl /help"

configure:5163: $? = 1

configure:5152: icl -v >&5

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.\

0.068 Beta Build 20130529

Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

icl: command line warning #10006: ignoring unknown option '/v'

icl: command line error: no files specified; for help type "icl /help"

configure:5163: $? = 1

configure:5152: icl -V >&5

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.\

0.068 Beta Build 20130529

Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

icl: command line warning #10155: ignoring option '/V'; argument required

icl: command line error: no files specified; for help type "icl /help"

configure:5163: $? = 1

configure:5152: icl -qversion >&5

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.\

0.068 Beta Build 20130529

Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

icl: command line warning #10006: ignoring unknown option '/qversion'

icl: command line error: no files specified; for help type "icl /help"

configure:5163: $? = 1

configure:5183: checking whether the C compiler works

configure:5205: icl       conftest.c   >&5

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.\

0.068 Beta Build 20130529

^M

Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

^M

^M

conftest.c

^M

link: cannot create link `conftest.obj' to `\357\273\277-out:conftest.exe': No such file or\

directory

configure:5209: $? = 1

configure:5247: result: no

configure: failed program was:

| /* confdefs.h */

| #define PACKAGE_NAME "MPICH2"

| #define PACKAGE_TARNAME "mpich2"

| #define PACKAGE_VERSION "1.5"

| #define PACKAGE_STRING "MPICH2 1.5"

| #define PACKAGE_BUGREPORT "mpich-discuss@mcs.anl.gov"

| #define PACKAGE_URL "http://www.mcs.anl.gov/research/projects/mpich2/"

| #define USE_SMP_COLLECTIVES 1

| /* end confdefs.h.  */

|

| int

| main ()

| {

|

|   ;

|   return 0;

| }

configure:5252: error: in `/usr/local/bin/mpich2-1.5':

configure:5254: error: C compiler cannot create executables

See `config.log' for more details

So Am I right to say that the problem comes from something else ?

I am trying to compile MPICH2 using the intel compiler. When using gcc, it compiles perfectly. Any ideas ?

 

Portrait de Casey

Stephane, 

    Try compiling the testcase in my post a few posts above yours (the same one Sergey quoted) or a simple hello-world.  Post your icl command line and the output of the compilation.  

Portrait de Sergey Kostrov

>>...See `config.log' for more details

Please upload it. Thanks.

Portrait de Stephane L.

Casey: I have just compiled a simple hello world using this command line:

icl example.c -o example

The output of the compilation is

Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.0.068 Beta Build 20130529
Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.

example.c
Microsoft (R) Incremental Linker Version 11.00.60610.1
Copyright (C) Microsoft Corporation.  All rights reserved.

-out:example.exe
example.obj

 So everything is fine and it runs perfectly.

Regarding the config.log file, the problem may be related to this output :

link: cannot create link `conftest.obj' to `\357\273\277-out:conftest.exe': No such file or directory

Portrait de Casey

This might be a longshot and I'm not too familiar with cygwin.  Configure is likely using a temp directory to compile its tests (e.g /tmp on linux), and you may either not have that setup or may not have write permissions to it.  Again, that might be a longshot but its worth looking at.

Connectez-vous pour laisser un commentaire.