Traceback option always on in the latest CVF 6.6c

[jeanvezina]

I have noticed that the traceback option is always left on

in the latest CVF 6.6C update, even with the highest

optimization levels selected. Does this may have an impact

on the executable efficiency ?

Example code:

!Check if the traceback option
!is on or off by deliberately
!producing a runtime error
character(5) abc
abc = ' '

read(abc,*)i ! An error will be produced here
end

Compile the code with the options /fast /opt:5 and

run it. The location of the error will be given. If this

has no impact on efficiency, this is fine.

Best regards,

Jean Vezina

[Steven_L_Intel1]

No. All /trace does is add some data to the executable that the traceback handler knows how to find. It may make your EXE a little bigger.

Is this a change? I wasn't aware anything had changed here.

[Steven_L_Intel1]

Fascinating. I have no idea what changed here. I can reproduce it - the driver is not passing -trace to the compiler, so I don't know what causes the traceback lineto appear.

It does not affect performance - enabling traceback adds a data section to the EXE, no code. It would make the EXE a bit bigger.

I'm "on the road" this week, but I'll try to figure out what changed when I get back.