On Thu, Sep 11, 2014 at 05:04:06PM -0700, Steve Kargl wrote:
What's the current status for running clang on sparc64?
Last time we played with this (february?) it was able to compile
a seemingly working world. So I guess it's not that terribly broken.
We didnt test that much stuff though.
In
On 12 Sep 2014, at 22:52, Andrey Chernov a...@freebsd.org wrote:
On 13.09.2014 0:44, Andrey Chernov wrote:
On 12.09.2014 22:40, Andrey Chernov wrote:
I don't have -current i386 combination, but I can try -current x64
later (with different -march).
It works on -current, amd64,
On Sat, Sep 13, 2014 at 10:23:22AM +0200, Roman Divacky wrote:
On Thu, Sep 11, 2014 at 05:04:06PM -0700, Steve Kargl wrote:
What's the current status for running clang on sparc64?
Last time we played with this (february?) it was able to compile
a seemingly working world. So I guess it's not
On Sat, Sep 13, 2014 at 09:51:35AM -0700, Steve Kargl wrote:
On Sat, Sep 13, 2014 at 10:23:22AM +0200, Roman Divacky wrote:
On Thu, Sep 11, 2014 at 05:04:06PM -0700, Steve Kargl wrote:
What's the current status for running clang on sparc64?
Last time we played with this (february?) it
On 13.09.2014 20:45, Dimitry Andric wrote:
After some massaging of gcc's source to disable its built-in segfault
handlers, I get this backtrace:
Do you get this with my core or finally able to reproduce it by yourself?
I think it's most likely this is some type of undefined behavior in gcc,
On 13 Sep 2014, at 20:00, Andrey Chernov a...@freebsd.org wrote:
On 13.09.2014 20:45, Dimitry Andric wrote:
After some massaging of gcc's source to disable its built-in segfault
handlers, I get this backtrace:
Do you get this with my core or finally able to reproduce it by yourself?
I was
