On Jul 5, 2014, at 11:42 AM, Gerald Pfeifer wrote:
> Farther below in wide-int.h, we define wide_int_storage as a class:
>
> class GTY(()) wide_int_storage
> {
> private:
>HOST_WIDE_INT val[WIDE_INT_MAX_ELTS];
>unsigned int len;
>unsigned int precision;
> :
>
> The patch below, w
On Sat, Jul 05, 2014 at 09:29:31PM +0200, Jakub Jelinek wrote:
> On Sat, Jul 05, 2014 at 09:25:50PM +0200, Gerald Pfeifer wrote:
> > On Sat, 5 Jul 2014, pins...@gmail.com wrote:
> > > This patch is fine but c++ allows class and struct be used
> > > interchangeable. If there is a compilers which do
On Sat, Jul 05, 2014 at 09:25:50PM +0200, Gerald Pfeifer wrote:
> On Sat, 5 Jul 2014, pins...@gmail.com wrote:
> > This patch is fine but c++ allows class and struct be used
> > interchangeable. If there is a compilers which does not it is broken
> > and should be report to them. Yes that means
On Sat, 5 Jul 2014, pins...@gmail.com wrote:
> This patch is fine but c++ allows class and struct be used
> interchangeable. If there is a compilers which does not it is broken
> and should be report to them. Yes that means clang is broken.
Clang does allow for it (it actually is the stage 1 co
> On Jul 5, 2014, at 11:42 AM, Gerald Pfeifer wrote:
>
> Farther below in wide-int.h, we define wide_int_storage as a class:
>
> class GTY(()) wide_int_storage
> {
> private:
>HOST_WIDE_INT val[WIDE_INT_MAX_ELTS];
>unsigned int len;
>unsigned int precision;
> :
>
> The patch b
Farther below in wide-int.h, we define wide_int_storage as a class:
class GTY(()) wide_int_storage
{
private:
HOST_WIDE_INT val[WIDE_INT_MAX_ELTS];
unsigned int len;
unsigned int precision;
:
The patch below, which I applied as obvious after a full bootstrap on
i386-unknown-fr
