<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - flang -E breaks fixed-format files"
href="https://bugs.llvm.org/show_bug.cgi?id=50993">50993</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>flang -E breaks fixed-format files
</td>
</tr>
<tr>
<th>Product</th>
<td>flang
</td>
</tr>
<tr>
<th>Version</th>
<td>12.0
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Frontend
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>David.Truby@arm.com
</td>
</tr>
<tr>
<th>CC</th>
<td>David.Truby@arm.com, jperier@nvidia.com, kirankumartp@gmail.com, llvm-bugs@lists.llvm.org, sscalpone@nvidia.com
</td>
</tr></table>
<p>
<div>
<pre>If the perprocessing-only step is run on a fixed-format Fortran file the
resulting output is no longer fixed-format. This can cause issues in build
systems that perform preprocessing and compilation separately and expect the
preprocessed file to still be valid fixed-format Fortran.
As an example, if you perform preprocessing like this:
flang -E file.f -o file.pp.f
flang file.pp.f
the resulting file will not compile as the compiler expects fixed-format
Fortran but that is no longer the case after preprocessing.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>