<HTML><BODY><p><br>No, it understands the intention of the person who wrote the code but this is an error.<br><br>@ gfortran 7.4.0</p><p>if(a == b) then<br>1<br>Error: Logicals at (1) must be compared with .eqv. instead of ==<br>gfort_test.f:15:9:</p><p>if(a .eq. b) then<br>1<br>Error: Logicals at (1) must be compared with .eqv. instead of .eq.</p><p><br>As far as I remember,some time ago to make the fortran code which compiles with ifort compile with gfortran the good starting point was to switch on all flags which control the strict use of the standard, unfortunately I have no access to ifort right now and can not check the proper combination, probably it was just "-std90". <br>By default, ifort compiles the non-standard code it is able to understand while the default gfortran behavior is to treat it as an error. This particular case is far beyond the standard, so I do not know if it is even possible to force gfortran to compile this code.<br><br>Sincerely,<br>Mikhail <br><br></p><p><br><br></p><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
Среда, 26 июня 2019, 8:43 +03:00 от "Fecher, Gerhard" <fecher@uni-mainz.de>:<br>
<br>
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<div id="style_15615278020164791749_BODY">Dear Gavin, <br>
Sorry my question was probably to short, it should read<br>
Does anyone know whether "== " works with gfortran ?<br>
<br>
With ifort the following test works well, but I cannot test it with gfortran<br>
The answer in the Intel forum that you quote does not include "=="<br>
<br>
program logicaltest<br>
implicit none<br>
!<br>
! test ==, .eq., .eqv.<br>
!<br>
logical a, b, c<br>
<br>
a=.true.<br>
b=.true.<br>
<br>
if(a == b) then<br>
write(6,*) 'a = b'<br>
end if<br>
<br>
if(a .eq. b) then<br>
write(6,*) 'a .eq. b'<br>
end if<br>
<br>
if(a .eqv. b) then<br>
write(6,*) 'a .eqv. b'<br>
end if<br>
<br>
end<br>
<br>
<br>
Ciao<br>
Gerhard<br>
<br>
DEEP THOUGHT in D. Adams; Hitchhikers Guide to the Galaxy:<br>
"I think the problem, to be quite honest with you,<br>
is that you have never actually known what the question is."<br>
<br>
====================================<br>
Dr. Gerhard H. Fecher<br>
Institut of Inorganic and Analytical Chemistry<br>
Johannes Gutenberg - University<br>
55099 Mainz<br>
and<br>
Max Planck Institute for Chemical Physics of Solids<br>
01187 Dresden<br>
________________________________________<br>
Von: Wien [wien-bounces@zeus.theochem.tuwien.ac.at] im Auftrag von Gavin Abo [gsabo@crimson.ua.edu]<br>
Gesendet: Mittwoch, 26. Juni 2019 03:37<br>
An: <a href="mailto:wien@zeus.theochem.tuwien.ac.at">wien@zeus.theochem.tuwien.ac.at</a><br>
Betreff: Re: [Wien] gfortran compilation and run problems for 19.1<br>
<br>
The == should work for C/C++ language. I don't recall ever seeing that being used for Fortran.<br>
<br>
A quote from a HP Doctor Fortran article [ <a href="https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/274462" target="_blank">https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/274462</a> ]:<br>
<br>
"The real trouble with making assumptions about the internal value of LOGICALs is when you try testing them for "equality" against another logical expression. The way many Fortran programmers would naturally do this is as follows:<br>
<br>
IF (LOGVAL1 .EQ. LOGVAL2) ...<br>
<br>
but the results of this can vary depending on the internal representation. The Fortran language defines two operators exclusively for use on logical values, .EQV. ("equivalent to") and .NEQV. ("not equivalent to"). So the above test would be properly written as:<br>
<br>
IF (LOGVAL1 .EQV. LOGVAL2) ..."<br>
<br>
On 6/25/2019 3:14 PM, Fecher, Gerhard wrote:<br>
<br>
Does == work ?<br>
<br>
Ciao<br>
Gerhard<br>
<br>
DEEP THOUGHT in D. Adams; Hitchhikers Guide to the Galaxy:<br>
"I think the problem, to be quite honest with you,<br>
is that you have never actually known what the question is."<br>
<br>
====================================<br>
Dr. Gerhard H. Fecher<br>
Institut of Inorganic and Analytical Chemistry<br>
Johannes Gutenberg - University<br>
55099 Mainz<br>
and<br>
Max Planck Institute for Chemical Physics of Solids<br>
01187 Dresden<br>
________________________________________<br>
Von: Wien [wien-bounces@zeus.theochem.tuwien.ac.at<mailto:wien-bounces@zeus.theochem.tuwien.ac.at>] im Auftrag von Sam Trickey [trickey@qtp.ufl.edu<mailto:trickey@qtp.ufl.edu>]<br>
Gesendet: Dienstag, 25. Juni 2019 15:13<br>
An: wien@zeus.theochem.tuwien.ac.at<mailto:<a href="mailto:wien@zeus.theochem.tuwien.ac.at">wien@zeus.theochem.tuwien.ac.at</a>><br>
Betreff: Re: [Wien] gfortran compilation and run problems for 19.1<br>
<br>
See below<br>
<br>
On 6/25/19 5:47 AM, Peter Blaha wrote:<br>
Hi,<br>
<br>
I can confirm the fix for inputpars.F. Of course, according to fortran standards a logical if should have an .eqv. operator (although I never "understood" what that should be good for ...).<br>
<br>
Keeps computer scientists occupied introducing needless and annoying distinctions.<br>
<br>
peace, Sam<br>
<br>
<br>
--<br>
Samuel B. Trickey<br>
QTP, Depts. of Physics and Chemistry<br>
2324 Physics Building<br>
Box 118435<br>
Univ. of Florida<br>
Gainesville, FL 32611-8435<br>
Vox: 352-392-6978 (direct)<br>
Vox: 352-392-1597 (receptionist)<br>
Fax: 352-392-8722<br>
<a href="http://www.qtp.ufl.edu/ofdft" target="_blank">http://www.qtp.ufl.edu/ofdft</a><br>
<a href="http://users.clas.ufl.edu/trickey" target="_blank">http://users.clas.ufl.edu/trickey</a><br>
<br>
<br>
_______________________________________________<br>
Wien mailing list<br>
<a href="mailto:Wien@zeus.theochem.tuwien.ac.at">Wien@zeus.theochem.tuwien.ac.at</a><br>
<a href="http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien" target="_blank">http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien</a><br>
SEARCH the MAILING-LIST at: <a href="http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html" target="_blank">http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html</a><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<br>-- <br>Mikhail Nestoklon<br></BODY></HTML>