[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Bus error on MacOS
- From: Coda Highland <chighland@...>
- Date: Mon, 6 May 2013 00:46:43 -0700
On Mon, May 6, 2013 at 12:38 AM, steve donovan
<steve.j.donovan@gmail.com> wrote:
> On Mon, May 6, 2013 at 1:17 AM, Jay Carlson <nop@nop.com> wrote:
>>
>> #ifdef __APPLE_CC__
>> #if defined(__i386__) && defined(__llvm__) && \
>> !defined(__clang__) && (__APPLE_CC__ == 5658)
>> asm("");
>> #endif
>> #endif
>
>
> This does not inspire confidence in clang! What else is going to go wrong,
> in some rather more complicated place?
>
> It's exactly the problem I was seeing with clang on Ubuntu, by the way,
> although there 'bus error' is spelt 'segfault'
>
> steve d.
Why doesn't this inspire confidence in clang? That says
!defined(__clang__), so doesn't this mean llvm-gcc?
/s/ Adam
- References:
- Re: Bus error on MacOS, Luiz Henrique de Figueiredo
- RE: Bus error on MacOS, Richter, Jörg
- Re: Bus error on MacOS, Luiz Henrique de Figueiredo
- Re: Bus error on MacOS, Luiz Henrique de Figueiredo
- Re: Bus error on MacOS, Luiz Henrique de Figueiredo
- Re: Bus error on MacOS, Dong Feng
- Re: Bus error on MacOS, Eric Wing
- Re: Bus error on MacOS, Jay Carlson
- Re: Bus error on MacOS, steve donovan