- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I traced a segfault to the clogf function, when compiling in 32 bits:
[prunet@horizon8 ~/essai]$ cat check_clogf.f90
program check_clogf
real(kind=4) :: a,b
a=0
b=1
print*,log(cmplx(a,b))
end program check_clogf
[prunet@horizon8 ~/essai]$ source /usr/local/intel/Compiler/bin/ifortvars.csh ia32
[prunet@horizon8 ~/essai]$ which ifort
/usr/local/intel/Compiler/composerxe-2011.3.174/bin/ia32/ifort
[prunet@horizon8 ~/essai]$ ifort -o check_clogf check_clogf.f90
[prunet@horizon8 ~/essai]$ ./check_clogf
Segmentation fault
however, when compiling in 64 bits, there is no problem:
[prunet@horizon8 ~/essai]$ source /usr/local/intel/Compiler/bin/ifortvars.csh intel64
[prunet@horizon8 ~/essai]$ which ifort
/usr/local/intel/Compiler/composerxe-2011.3.174/bin/intel64/ifort
[prunet@horizon8 ~/essai]$ ifort -o check_clogf check_clogf.f90
[prunet@horizon8 ~/essai]$ ./check_clogf
(0.0000000E+00,1.570796)
I checked that the double precision (clogd) function does not have this problem.
I wonder if this is a known bug ?
Cheers,
Simon
[prunet@horizon8 ~/essai]$ cat check_clogf.f90
program check_clogf
real(kind=4) :: a,b
a=0
b=1
print*,log(cmplx(a,b))
end program check_clogf
[prunet@horizon8 ~/essai]$ source /usr/local/intel/Compiler/bin/ifortvars.csh ia32
[prunet@horizon8 ~/essai]$ which ifort
/usr/local/intel/Compiler/composerxe-2011.3.174/bin/ia32/ifort
[prunet@horizon8 ~/essai]$ ifort -o check_clogf check_clogf.f90
[prunet@horizon8 ~/essai]$ ./check_clogf
Segmentation fault
however, when compiling in 64 bits, there is no problem:
[prunet@horizon8 ~/essai]$ source /usr/local/intel/Compiler/bin/ifortvars.csh intel64
[prunet@horizon8 ~/essai]$ which ifort
/usr/local/intel/Compiler/composerxe-2011.3.174/bin/intel64/ifort
[prunet@horizon8 ~/essai]$ ifort -o check_clogf check_clogf.f90
[prunet@horizon8 ~/essai]$ ./check_clogf
(0.0000000E+00,1.570796)
I checked that the double precision (clogd) function does not have this problem.
I wonder if this is a known bug ?
Cheers,
Simon
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I cannot reproduce the bug with your code using IFort 12.0.3-32bit on Suse X64.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you read this article? It has suggestions for diagnosing seg violations:
http://software.intel.com/en-us/articles/determining-root-cause-of-sigsegv-or-sigbus-errors/
http://software.intel.com/en-us/articles/determining-root-cause-of-sigsegv-or-sigbus-errors/

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page