<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/56764>56764</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            Are module files in LLVM Flang platform/target agnostic?
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            flang
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          mstorsjo
      </td>
    </tr>
</table>

<pre>
    If cross compiling with Flang, e.g. I've built the flang executable on x86_64 linux, but I invoke `flang-new` with `--target=aarch64-windows`, Flang would end up including module files that have been generated by the build of `flang-new` for its default target instead of the target I'm currently compiling for. Are those module files usable for other targets than the one they were generated for?

(I'm aware that flang isn't entirely ready for all cross compilation use - I'm trying to take baby steps towards making it work in such cases.)

This issue was brought up for discussion in https://reviews.llvm.org/D130349#3674498.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxlk1uPmzAQhX8NvIyCwNzCAw_bRpFW2r5Vfa0MHsC7Bke-hM2_79iJuo0qRcRg5pxvzphBi1v_OsFotLUw6vUildxm2KVb4Kz4NifsO2A2Z_CasPaKMHipHLgFYQrbgJ84escHhaA3-Dw2v5sKSMN_hsrBO3gFuV31B0LS5LHmsOFO67sJLQ4Hx82MLilPnJtxaarDLjehd0ubQSWCwK69EoCbAH8hyVF5EVBXLTyZT1KhJS7uYOGBE3GDGTc03KGA4RaZA70APf3HMmkD0lkQOHEfGoxEZGMd8lgRyh9PQxQrjN4Y3Jy6_ZMbyWTwYujNRVt8ZvM2phScNImZh1qE3qK83kIh3mBHkviCp5KkPCf5KclfHld2vEPwnUc3avs-D2k32nCUk5MGCc4Q_y26cqWeBs2dpJF54jw8WnLmFrpwmthoYAOn2CiACzFqMhIWVv4R3pCOxmE-KB-wflxg5BZtlrDuX8ifi7TEYz3Czi0MRvt5cWF6gUZIO3prAwKpLM5dbFJSY2f6GbxK3G2m1HXNtKFDeD4VZV5WXcLKsmmrqjtmKfZFUx-7ummqKhV9Kbqy46mTTmEfZvCUPnm8vf368ThLF2qeIFYSfsyUz5u2To4UdOqN6p-BZjqqfsgoN7oJVI-_w8Xodxwd3cZGLS3qpm2qdOm7gZdFfjy27dAcu64QRdPyYir42I1Yl12q-IDK9kn9LWFsun9sLKlPqexZzljespYVRcvKDDmOE-l2mDORl3VS5bhyqf4GlJo-4gx-trSppHVf6aWcYp43xGhF-tzT8TT9ap029l2nEb2P3H8A-kNcgA">