Issues with flang-16, flang-17

[Alastair McKinstry]

Hi

Yes, if issues are discovered with flang* they should be reported upstream.

What I'm currently planning is that for relevant packages (eg fckit, the 
Fortran wrapper API to the ECMWF toolkits) I do a build that compiles 
and runs testsuites for both(*) compilers, do a build for experimental 
and allow the package to fail; meanwhile a separate build with 
gfortran-only goes to unstable.

regards

Alastair

(*) We can build with gfortran, flang, flang-to-external-fc, maybe lfortran.


On 01/12/2023 09:17, Sylvestre Ledru wrote:
> Hello
>
> apt.llvm.org provides flang packages too.
> If there are issues with flang, you should report them upstream, no ? :)
> and afaik, there are also some automation upstream.
>
> Also, don't hesitate to provide test cases.
>
> thanks
> SYlvestre
>
> Le 01/12/2023 à 10:13, Alastair McKinstry a écrit :
>> Hi,
>>
>> Now that flang-* and flang-to-external-fc-* are in Debian LLVM, I've 
>> been testing rebuilds of Fortran codes and libraries.
>>
>> The results haven't been good: flang-16 won't compile a simple 
>> hello.f90 (fair enough, I'm testing flang-17* instead).
>>
>> So If I enable test builds, what will we do in Debian for crashes, 
>> ICEs? I can report upstream but it would be good to build a CI/CD 
>> pipeline.
>>
>> What currently exists, and whats your opinion?
>>
>> regards
>>
>> Alastair
>>
>
-- 
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alastair at mckinstry.ie, im: @alastair:mckinstry.ie