Bug 201270 - lang/luajit is broken under clang
Summary: lang/luajit is broken under clang
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Sergey A. Osokin
URL:
Keywords:
Depends on:
Blocks: 205582
  Show dependency tree / graph
 
Reported: 2015-07-02 10:08 UTC by Roman Tsisyk
Modified: 2018-09-03 19:30 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (osa)

Attachments
a test case for broken C++ unwind under clang (243 bytes, text/plain)
2015-07-02 10:08 UTC, Roman Tsisyk 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Tsisyk 2015-07-02 10:08:20 UTC 
Created attachment 158254 [details]
a test case for broken C++ unwind under clang

http://www.freelists.org/post/luajit/External-unwind-is-broken-on-FreeBSD-10-x86-64


```
Program received signal SIGSEGV, Segmentation fault.
0x0000000800b66c1e in __cxa_end_catch () from /lib/libcxxrt.so.1
(gdb) bt
#0  0x0000000800b66c1e in __cxa_end_catch () from /lib/libcxxrt.so.1
#1  0x0000000000401d50 in lbox_call ()
#2  0x0000000000401c4d in main ()
```

LuaJIT v2.0.4

% uname -a
FreeBSD freebsd.local 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11
21:02:49 UTC 2014 root@xxxxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC
amd64

% c++ --version
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.1
Thread model: posix

The same tests case works fine with gcc48.
Comment 1 Veniamin Gvozdikov freebsd_committer freebsd_triage 2015-07-02 10:15:10 UTC 
That bug actually with clang on base system, although related to luajit code.

vg@freebsd:~ % uname -a
FreeBSD freebsd.local 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
vg@freebsd:~ % clang -v
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.1
Thread model: posix
Selected GCC installation:
Comment 2 Veniamin Gvozdikov freebsd_committer freebsd_triage 2015-07-02 10:15:18 UTC 
That bug actually with clang on base system, although related to luajit code.

vg@freebsd:~ % uname -a
FreeBSD freebsd.local 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
vg@freebsd:~ % clang -v
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.1
Thread model: posix
Selected GCC installation:
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-02-07 14:42:45 UTC 
Seems overcome by events?