Re: integer*8 speed vs integer*4 speed

Hi Steve,

Because my current F77 compiler does not support integer*8 and
logical*8. I am trying to move to the IVF 9.1 compiler but am having
many, many problems for my mixed F66 / F77 code (mostly zero
initialization problems).

If you need help, you can post in our user forum or contact Intel
Premier Support. See if the options /Qsave /Qzero help you.

I have been doing this port for about 2 years now. It always gets thrown to the back burner for other issues though. At the moment
I have some weird compile errors in my C++ code so I have to get those fixed first.

Thanks,
Lynn McGuire

.

Relevant Pages

  • Re: OT: Requesting C advice
    ... some behind the scenes action of the compiler. ... In fact the memory could ... Proper initialization means that floats and doubles must be initialized to 0.0 and pointers must be initialized to the null pointer value, even if those bit patterns differ from all-bits-zero. ...
    (Fedora)
  • Re: I think C# is forcing us to write more (redundant) code
    ... static void F(out string s) ... >> compiler enforced). ... locals here and locals are stack allocated, ... I don't have a problem with this explicit initialization in the current ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: memory management in Ada: tedious without GC?
    ... I don't like the permission to reorder operands, ... May the compiler group A and C and initialize both them by zeroing memory? ... If the initialization order were fixed, that would be illegal to do. ... subprograms, not as a pragma Pure, but as a contract. ...
    (comp.lang.ada)
  • Re: pointer and storage
    ... But, as always, a compiler is free to issue any diagnostics it ... If the initialization is executed, it invokes undefined behavior. ... In old versions of the C language, before "const" was introduced, this ...
    (comp.lang.c)
  • Re: Solving Lazy Initialization and double checked locking problem
    ... Hey Roger, ... Now the compiler is bound to keep them in straight order. ... >> I have been thinking about the lazy initialization and double checked ... >> syncronized method and the variable is volatile, the HeavyObject will be ...
    (comp.lang.java.programmer)