On 03/12/18 13:54, Dimitry Andric wrote:
> On 12 Mar 2018, at 16:03, Dimitry Andric wrote:
>> On 12 Mar 2018, at 00:56, Ian FREISLICH
>> wrote:
> ...
>>> I haven't got avr-gcc to compile yet.
>> No idea about this, is it very different from regular gcc's? As those
>> all compile fine now.
> For
On 12 Mar 2018, at 16:03, Dimitry Andric wrote:
>
> On 12 Mar 2018, at 00:56, Ian FREISLICH wrote:
...
>> I haven't got avr-gcc to compile yet.
>
> No idea about this, is it very different from regular gcc's? As those
> all compile fine now.
For avr-gcc, which is an older version of gcc with
On Mon, Mar 12, 2018 at 04:03:44PM +0100, Dimitry Andric wrote:
> On 12 Mar 2018, at 00:56, Ian FREISLICH wrote:
> >
> > There's been some fallout in ports land since clang-6 around null
> > pointer arithmetic and casts. I cannot think of a good reason for doing
> > the following but then I've n
On 12 Mar 2018, at 00:56, Ian FREISLICH wrote:
>
> There's been some fallout in ports land since clang-6 around null
> pointer arithmetic and casts. I cannot think of a good reason for doing
> the following but then I've not dabbled in the arcane much:
>
> # define __INT_TO_PTR(P) ((P) + (char
Ian FREISLICH writes:
> /usr/ports/lang/v8/work/v8-3.18.5/out/native/obj.target/v8_base.x64/src/type-info.o../src/stub-cache.cc:1477:33:
> error: reinterpret_cast from 'nullptr_t' to 'char *' is not allowed
> : GetCodeWithFlags(flags, reinterpret_cast(NULL));
>
The problem is even worse on armv6/armv7/aarch64, and much worse on
powerpc64/sparc64, which still have gcc in base.
I have not been saving up the emails where ports committers have been
fixing various failure modes. I hesitate to start making harmless-
seeming patches myself for fear of my non-e
