Search results for query: *

Thanks, xwb! Sorry for not answering before, But really thanks. I've never thought about independent allocation of arrays into a type structure. That's a marvelous idea! I'll make some trials on this, and let you know when I have some extra results. But this is the tip of the year! :) Thanks...

Thanks a lot! I'll be waiting here for that. :) Really thanks, and sorry for taking so much of your time (in all question I've already made here. :D ).

Hi xwb. Thanks for the help, but I really could not properly understand your answer this time. :) Despite not being as used to pointers as to matrices, I don't see how they could help me to avoid useless usage of memory and keep the free input defined arrays size. To put in a real example...

Hi all. Well, this is the most difficult task I've seen, and probably the answer is "it can't be done". But I need to be sure about it. In order to avoid an extremely big and heavily zeroed matrix, whose size is fully dependent of input parameters, I came out with the idea of a looping code...

Thanks a lot, xwb! Just a bit more: In case of reals, real in a 32 bits system should be specified as a real*8 in a 64 bits machine, while real*16 and double precision would mean the same in both 32 and 64 bits machines, correct? Also, about aligning, it just concerns about derived types...

Thanks, xwb. Just asking a bit more: the second piece of the aswer is a only way to "boost" a fortran program, not considering the 64 or 32 bits, correct? Is there anything that I'm not noticing that could make explicit use of the 64 bits to accelerate a fortran code? About the first piece...

Hi all. I'm having some serious doubts about the porting code from 32-bits to 64-bits subject. Basically, since all the documentation about such a subject that I find is clearly directed to C and C++ useres, it becomes useless for me. I would like to know when, where and how some pieces of...

Hi xwb! Well, nfortunatelly, at this time it can't be the bounds of the array. Cause it's not making sense, since I'm not trying to access a positon out of the bounds, neither trying to "write" something in the array but out of it's bounds. The thing that goes wrong, and is absolutelly...

Ok, those are two questions. First one: have anybody here already got an deallocation error (maybe with ifort 8.1)? I'm using it, and in a program with a hell of variables, I just tracked down an "forrtl: severe (174): SIGSEGV, segmentation fault occurred" error to the deallocation of a...

Thanks, xwb. ;) "len_trim", you mean. ;) This is one of the updates for this program. I just knew about tis intrinsic after writing this code, while working on another one. ;) But thanks for that too. ;)

God! Thanks a lot, guys, it would take centuries for me find that! Just 6 months without programming, and already making these sort of mistakes? :P xwb: just to let you know, it means "header of file damaged". ;) And there I just forgot to put the sentence between '...'. Anyway, thank you...

Ok, news from here. I decide to step back on the code, and move forward on it's writing again, on a slower pass. So, I got the old version of the code, with everything straigh written on it, broke one-by-one the 3 subroutines and placed it in the same file as the main program with a...

Evil ISP here. :P Ok, my english is not that good, so I didn't understand or didn't use equivalence or aliasing via parameters. I don't use comon block (hate them!) all arrays are properly allocated. Any other idea? Thanks for everything in advance! ;)

Hi! Just tried that. Not too much hope, anyway. Well, the arrays sizes, as well as "natomtot" integer value are correct. And the "origem" array values keep on being changed by someone who doesn't care about it... [thumbsdown] Any idea around? [ponder]

Hi all! Well, this is my first post in this forum, and I hope one of few related to "problems"... :P I've tried this compilation already on ifort 8.1, compaq visual fortran 6.5 and pgf90 (unknown version). Each compiler is on a different machine. In all cases, it gives me: forrtl: severe...