Search results
Create the page "PGI Fortran compiler" on this wiki! See also the search results found.
- '''''[[Supported compilers for GEOS-Chem|Previous]] | [[Intel Fortran Compiler|Next]] | [[Guide to compilers for GEOS-Chem]]''''' #<span style="color:blue">'''The GNU Fortran compiler (aka gfortran)'''</span>52 KB (7,498 words) - 17:56, 24 October 2023
- |[[#Bug fixes for the PGI compiler|Bug fixes for the PGI compiler]] === Bug fixes for the PGI compiler ===99 KB (15,209 words) - 20:26, 20 September 2022
- === GCHP silent bug when using gfortran compiler === Compiling GCHP versions prior to 12.5.0 with GCC compiler gfortran results in silent bug where the Olson land mask is assigned all ze70 KB (10,330 words) - 21:56, 20 December 2019
- #*Will enable full use of gfortran compiler ...for netCDF-Fortran in Makefile_header.mk|Add a more robust test for netCDF-Fortran in Makefile_header.mk]]41 KB (6,194 words) - 14:22, 22 March 2021
- The NcdfUtilities package contains Fortran modules that you can use to write data to and read data from netCDF files. NcdfUtilities contains the Fortran source code files listed below. These same files are used both in GEOS-Che20 KB (3,149 words) - 20:10, 22 May 2017
- ...ime to execute. If your computer system has the [https://gcc.gnu.org/ GNU Compiler Collection (GCC)] already installed (as do most modern Unix/Linux clusters) This will add the following compiler switches to the compilation sequence:16 KB (2,242 words) - 14:12, 10 June 2019
- ...compiler#File Linking Error|Bug fix for linking files when compiling with PGI]] ...es_for_GEOS-Chem_v11-01|Add further fixes for compiling GEOS-Chem with PGI Fortran]]95 KB (13,968 words) - 21:57, 20 December 2019
- ...m_v9-01-03#Bug_fix_for_Intel_Fortran_Compiler_12|Bug fix for Intel Fortran Compiler 12]] === Bug fix for Intel Fortran Compiler 12 ===38 KB (5,526 words) - 15:22, 19 June 2019
- === Flexible precision was introduced in Fortran-90=== In most Fortran codes (including GEOS-Chem) you will see declarations such as:21 KB (3,003 words) - 15:39, 19 June 2019
- ...|Fixed a seg fault error in HEMCO v2.0 that was caused by an Intel Fortran compiler bug]] ...|Fixed a seg fault error in HEMCO v2.0 that was caused by an Intel Fortran compiler bug]]166 KB (26,088 words) - 18:43, 28 May 2020
- ...Implement_ISORROPIA_v2.0_as_a_Fortran_module|Implement ISORROPIA v2.0 as a Fortran module]] ...iable_from_Makefile_header.mk_for_a_cleaner_build_sequence|Removed the <tt>COMPILER</tt> variable from <tt>Makefile_header.mk</tt> ]]158 KB (24,655 words) - 18:49, 28 May 2020
- ...ugs|our ''Known issues caused by compiler bugs'' wiki page]] for a list of compiler-related issues and workarounds. ...ISORROPIA_v2.0_as_a_Fortran_module|(v11-02a) Implement ISORROPIA v2.0 as a Fortran module (eliminating <code>COMMON</code> blocks)]]33 KB (5,225 words) - 20:46, 2 January 2019
- ...h <tt>0.0d0</tt>, etc.). This will prevent compilation errors for the PGI compiler. (For more information about double-precision exponents, please see the [h ...mpiling GEOS-Chem with the [[Intel Fortran Compiler#IFORT 10|Intel Fortran Compiler version 10]] (aka IFORT 10) when selecting <tt>-O2</tt> optimization and <t36 KB (5,768 words) - 15:06, 19 June 2019
- ...as following. I run the model on a LINUX cluster with LINUX/IFORT (64-bit) compiler. The processor number I set is 32 for 4 threads. ...that was compiled with the [[Intel_Fortran_Compiler#IFORT_10|Intel Fortran Compiler version 10]] (Build 20080312 Package ID: l_fc_p_10.1.015). I was able to r23 KB (3,442 words) - 17:39, 15 November 2017
- :However, if you run the model (I used 4x5 resolution, ifort v10 compiler,4 cores) ALL the dry deposition species are dumped out. :In my testing/debugging, the compiler found another problem: in <tt>gamap_mod</tt>, line 1313 and forward (init_t15 KB (2,286 words) - 17:40, 15 November 2017
