Andrew Pinski wrote:
> On Mon, Aug 22, 2016 at 9:42 AM, Andy Ross wrote:
> > I don't follow. There's no change to the ABI, the generated code is
> > identical in all cases. Can you explain what you mean?
>
> The encoding of int and long are different in C++. S
Andrew Pinski wrote:
> Why do you think the above code does not have a bug in it? int32_t
> is long and changing it now is changing the ABI (especially for
> C++).
I don't follow. There's no change to the ABI, the generated code is
identical in all cases. Can you explain what you mean?
The pro
Same code. Includes an attempt to format a change log entry in a more
gcc-friendly way. I'm new here.
>From c208b51fb55c6758c1059dfaee398c27da398e9d Mon Sep 17 00:00:00 2001
From: Andy Ross
Date: Fri, 19 Aug 2016 09:40:42 -0700
Subject: [PATCH] newlib-stdint.h: Remove 32 bit longs
Th
The reproduction is straightforward. Just build any cross gcc with
--enable-newlib (e.g. the one in the Zephyr SDK) and compile this
(on any 32 or 64 bit 2's complement architecture) with newlib's
headers.
#include
extern void takes_fmt(const char *fmt, ...)
__attribute__ ((form
. It seems whatever requirement this was honoring isn't
valid anymore.
>From 784fb1760a930d0309f878bbae7bfd38137f5689 Mon Sep 17 00:00:00 2001
From: Andy Ross
Date: Fri, 19 Aug 2016 09:40:42 -0700
Subject: [PATCH] newlib-stdint.h: Remove 32 bit longs
This would make __INT32_TYPE__ a &quo
