Issues with compiler flags in gfortran

[Chris Jones]

On 22/01/2019 4:43 am, Nicolas Pavillon wrote:
> Hi,
> 
> Thanks for the pointer, that indeed does the trick, and compilation 
> works perfectly in both cases (w/o cctools or with cctools+Xcode). I had 
> tried to select as through compiler flags, but I guess this did not 
> affect what gfortran was calling.
> 
> However, this then does not solve the underlying issue, For what I 
> understand, the llvm70 variant of cctools is made the default to ensure 
> reproducibility in some builds, but this also comes at a serious cost in 
> terms of compiler optimization with such older tools, isn’t it?

The MacPorts provided as, from cctools, is *supposed* to be the same as 
that provided by Xcode 10. Actually, one thing you have not said is what 
macOS version are you using ?

Chris

> 
> Cheers,
> 
> Nicolas
> 
> 
>> On Jan 22, 2019, at 11:23, Chris Jones <jonesc at hep.phy.cam.ac.uk 
>> <mailto:jonesc at hep.phy.cam.ac.uk>> wrote:
>>
>> Hi,
>>
>> Could you then please try either removing the cctools package, or 
>> reinstall it with the xcode variant. Either should result in the build 
>> using the xcode provided as instead.
>>
>> Chris
>>
>> On 21 Jan 2019, at 3:54 pm, Nicolas Pavillon <nicos at macports.org 
>> <mailto:nicos at macports.org>> wrote:
>>
>>> Hi,
>>>
>>> I just tried that, and I think I have been using the current default:
>>>
>>> NicolasMacBook:~ nicos$ port installed cctools
>>> The following ports are currently installed:
>>>   cctools @921_0+llvm70 (active)
>>>
>>> The reason I have been mentioning how old as might be is that the one 
>>> provided by cctools returns version 1.38, which quite behind compared 
>>> to the version provided by binutils, for example.
>>>
>>> /opt/local/bin/as -v
>>> Apple Inc version cctools-921, GNU assembler version 1.38
>>>
>>> Cheers,
>>>
>>> Nicolas
>>>
>>>> On Jan 22, 2019, at 0:23, Chris Jones <jonesc at hep.phy.cam.ac.uk 
>>>> <mailto:jonesc at hep.phy.cam.ac.uk>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> What exactly version (and variants) of cctools do you have installed ?
>>>>
>>>> Perhaps try force removing it, then reinstall, to make sure you are 
>>>> using the current default variants.
>>>>
>>>> Chris
>>>>
>>>> On 21 Jan 2019, at 2:47 pm, Nicolas Pavillon <nicos at macports.org 
>>>> <mailto:nicos at macports.org>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I stumbled on some issues with the fortran compiler that I cannot 
>>>>> really understand. They might be linked with other topics discussed 
>>>>> recently about cctools, but it still seems somewhat different.
>>>>>
>>>>> This happens with the port OpenBLAS, where the compilation fails 
>>>>> when flags to compile AVX instructions yield errors during 
>>>>> compilation, as described in the following tickets:
>>>>> https://trac.macports.org/ticket/57912
>>>>> https://github.com/xianyi/OpenBLAS/issues/1951
>>>>>
>>>>> However, when I tried even more basic flags such as -march=native, 
>>>>> compilation also fails with errors such as
>>>>> /var/folders/x8/q7j02h4d661_p7cjh42_jh380000gn/T//ccqkNy6A.s:103:no 
>>>>> such instruction: `vxorps %xmm0, %xmm0,%xmm0'
>>>>>
>>>>> I then tried with another gfortran compiler outside of macports, 
>>>>> and it could compile without any issue if I remove macports’ prefix 
>>>>> from the path, which seems to indicate that the issue is coming 
>>>>> from the assembler in macports.
>>>>>
>>>>> My best guess is that as in cctools is too old, but I am not sure 
>>>>> about that. Also, if it is correct, I wonder how this could be 
>>>>> solved. Any ideas?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Nicolas 
>>>
>