<html>#2515: work around compiler issues with empty OMP continuation lines
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>When splitting long Fortran input lines created eg by the various <code>CCTK_</code> macros there is a chance to create lines that the Intel and or GNU compilers will not accept.</p>
<p>In particular ifort and gfortran handle OMP continuations with only space differently. ifort will not accept something like "!$OMP& &" ie only spaces between the & while gfortran will not accept "!$OMP " ie only spaces.<br />
This triggers when breaking up constructs like:</p>
<div class="codehilite"><pre><span></span>$!OMP parallel private(i)
</pre></div>
<p>that need to be rendered as (gfortran):</p>
<div class="codehilite"><pre><span></span>$!OMP parallell&
$!OMP& &
$!OMP&private(i)
</pre></div>
<p>and (ifort)</p>
<div class="codehilite"><pre><span></span>$!OMP parallell&
$!OMP
$!OMP&private(i)
</pre></div>
<p>neither of which the other one accepts.</p>
<p>This prevents compiling of the current ET code for TestLoopFortran.F90 git hash <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/commits/aa49005bf0afa0625d4e78585a594fc12e9ed5f3" rel="nofollow">aa49005b</a> "Cactus: make HTML docs work for thorns not using cactus style file" of <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus" rel="nofollow">cactus</a> on eg Comet with the intel compiler in use there.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2515/work-around-compiler-issues-with-empty-omp'>https://bitbucket.org/einsteintoolkit/tickets/issues/2515/work-around-compiler-issues-with-empty-omp</a></p>
</html>