[cfe-dev] Clang should natively support fortran

[Dimitry Andric via cfe-dev]

On 23 Jun 2016, at 01:36, Renato Golin via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> 
> On 22 June 2016 at 23:15, Yuri via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>> I guess the real question is: what is the best replacement of an unwind API?
>> Does clang/llvm supply it? Or what is the best solution of this problem?
> 
> LLVM has a sub-project called libunwind (same as the other one, sorry
> for the bad naming).
> 
> http://llvm.org/viewvc/llvm-project/libunwind/trunk/
> 
> It's fairly active and mostly functional. I believe FreeBSD may
> already use it (or some other non-gcc one) internally with Clang, so
> you should just try to find it. It works pretty well with Compiler-RT
> and libc++, and I believe both are also aready being used by Clang in
> FreeBSD.

Yes, Ed imported it into FreeBSD head 8 months ago:

https://svnweb.freebsd.org/base/head/contrib/llvm/projects/libunwind/

However, it is currently only used for AArch64 and RISC-V.


> I have no idea, though, if the ageing GCC in FreeBSD will work with
> libunwind, libc++ or compiler-RT. Actually, I'd be very surprised if
> it did... :(

Nope, we only keep gcc 4.2 for some architectures such as PowerPC and Sparc.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160623/56313dfc/attachment.sig>