Anyone know for clang 3.8.0 or devel/powerpc64-gcc based and WITH_LIBCPLUSPLUS=
(use of libcxxrt and libc++ for the system) which _Unwind_RaiseException
implementation is supposed to be used for TARGET_ARCH=powerpc?
TARGET_ARCH=powerpc64? Alternatives around include:
/usr/src/contrib/llvm/proje
On 20-2-2016 16:50, Dimitry Andric wrote:
> On 20 Feb 2016, at 16:09, Willem Jan Withagen wrote:
>>
>> I'm trying to build a port of Ceph for FreeBSD, which is sort of trying
>> to shoot at a tank with a watergun :)
>
> This is very nice, it would be good to have Ceph on FreeBSD. Note that
>
On 20 Feb 2016, at 16:09, Willem Jan Withagen wrote:
>
> I'm trying to build a port of Ceph for FreeBSD, which is sort of trying
> to shoot at a tank with a watergun :)
This is very nice, it would be good to have Ceph on FreeBSD. Note that
if you have problems with porting, usually the free
On 20-2-2016 16:09, Willem Jan Withagen wrote:
> I'm trying to build a port of Ceph for FreeBSD, which is sort of trying
> to shoot at a tank with a watergun :)
>
> There are 2 things to porting burdens:
> Linux <> FreeBSD
> GCC <> Clang
>
> So I'm not sure whether to error below
I'm trying to build a port of Ceph for FreeBSD, which is sort of trying
to shoot at a tank with a watergun :)
There are 2 things to porting burdens:
Linux <> FreeBSD
GCC <> Clang
So I'm not sure whether to error below is due a GCC-ism that is not
suppoted by the 3.7.1 Clang we
On 20-2-2016 15:37, Dimitry Andric wrote:
> On 20 Feb 2016, at 15:31, Willem Jan Withagen wrote:
>>
>> Before I actually dump the problem here.
>> Would this be the place to ask about include files that give errors for
>> code compiling under GCC but not under Clang 3.7??
>>
>> gcc version 4.8.3 2
On 20 Feb 2016, at 08:33, Alex Denisov <1101.deb...@gmail.com> wrote:
>> On 20 Feb 2016, at 01:57, Steve Kargl
>> wrote:
>>
>> If anyone is interesting fixing FreeBSD's C compiler, it
>> would be appreciated.
...
>> foo.c:21:1: error: use of undeclared identifier 'corrupt'; did you mean
>> 'cry
On 20 Feb 2016, at 15:31, Willem Jan Withagen wrote:
>
> Before I actually dump the problem here.
> Would this be the place to ask about include files that give errors for
> code compiling under GCC but not under Clang 3.7??
>
> gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC)
>
> FreeBSD cla
Hi,
Before I actually dump the problem here.
Would this be the place to ask about include files that give errors for
code compiling under GCC but not under Clang 3.7??
gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC)
FreeBSD clang version 3.7.1 (tags/RELEASE_371/final 255217) 20151225
Target:
On 20 Feb 2016, at 09:34, Roman Divacky wrote:
> Fwiw, I've just committed the patch to clang in r261422. You might want
> to keep using a local modification or ask dim@ to import that patch
> to our copy of 3.8.
I've asked the LLVM release manager to consider merging this into the
3.8 branch. T
C compilers are always doing best effort attempts to report when you feed them
code that is not valid C.
For example, in this case:
On 20 Feb 2016, at 00:57, Steve Kargl wrote:
> if (i > 0)
> goto corrupt;
This is valid, as long as you have a label called corrupt to look for. You do
n
Thanks!
llvm bugzilla's 26605 did not having anything yet for this so I've copied over
your note. But I've left the status alone.
The next thing that I ran into looks nastier: c++'s exception handling is
broken.
#include
int main(void)
{
try { throw std::exception(); }
catch (std::e
Fwiw, I've just committed the patch to clang in r261422. You might want
to keep using a local modification or ask dim@ to import that patch
to our copy of 3.8.
Thanks for your diagnosis and testing!
Roman
On Thu, Feb 18, 2016 at 02:29:29PM -0800, Mark Millard wrote:
> On 2016-Feb-17, at 9:23 PM,
13 matches
Mail list logo
