Federico Perini

[Cases](https://github.com/fortran-lang/fpm/pull/847#issuecomment-1464826169) were made against relaxing the directory structure constraitns. However, one option wout be to mimic Cargo: Temporary (per build): ``` FPM_BUILD_DIR=custom_build_folder fpm build ``` Manifest: ``` [build] target-dir =...

My understanding of the fortran features structure is to hide compiler details behind the flags, so I'm not 100% sure adding compiler-specific flags is the best approach here. Regarding max...

I agree, would probably make the most sense to have them under the `[build]` table? I.e. Cargo has `rustflags`, we may have something like this? ```toml [build] link = ["blas","lapack"]...

Exactly, that's why flags for shared Fortran features are standardized via the `[fortran]` table and internally resolved: https://github.com/fortran-lang/fpm/blob/1cfcaf8aeb9f428b78cfbac2a23e7a9842be65e9/src/fpm_compiler.F90#L160-L174 so I think this structure seems preferable. For example for unlimited line...

Lots to think about! Thinking about it, I believe that profiles and assignment of compiler-specific flags are two different topics. 1) For compiler flags, we just need to standardize this...

This issue has been discussed several times, and Intel has reported to be working on a fix: https://fortran-lang.discourse.group/t/the-same-named-entity-from-different-modules-and-or-program-units-cannot-be-referenced-bug/7387

Yes, unfortunately I also noted this a while ago: https://github.com/fortran-lang/fpm/blob/7535cab6efc89dd5a294f0d9643b5eebd6b237f0/src/fpm_meta.f90#L139-L142 I have never had time to dig into the issue, though. I don't use openmp much, but I believe every...

Regarding the filesystem tests, it would seem like it may be enough to ensure that the test file name is different from each thread.

OK [I see](https://godbolt.org/z/Y58h4WvMf), thank you @jvdp1. It seems like the test program requires ~10G elements, which is more than the max number of elements that an `int32` integer can store....

@jvdp1 @jalvesz I suggest we limit this PR to your bugfix and merge it soon. Concerning the larger `ilp64` effort, I think it deserves a separate PR.