Hi,
I finally had a chance to work on this on Mountain Lion.
I build g95 uncommenting the blacklist for clang.
I was not able to reproduce the problem with clang.
> because of the clang version?
Presumably. The buildbot mtln has clang 421.11.66, but I have clang
503.0.40 (/usr/bin/clang).
What
On 2014-10-19 08:08 , Takeshi Enomoto wrote:
> fcomp is a comparison and a pop without a size, but
> I'm not sure if I should add s (32-bit) or l (64-bit).
> For example fmuls and movl are used before and after fcomp in line 412.
>
> I don't speak assembler. Could anyone help me with asm?
> Commen
Dear Ryan and all,
> This is unusual. What's the basis for this? Is it because of libstdc++? or
> because of the clang version? or something else?
Thank you for noting this. This is not related to libstdc++ because g95 is
written in C.
Probably it is due to clang version.
Clang is somewhat str
> On Oct 18, 2014, at 7:05 AM, take...@macports.org wrote:
>
> Revision
> 126963
> Author
> take...@macports.org
> Date
> 2014-10-18 05:05:00 -0700 (Sat, 18 Oct 2014)
> Log Message
>
> g95: blacklist clang on Lion and Mountain Lion
> Modified Paths
>
> • trunk/dports/lang/g95/Portfile
>
