This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH C++] Fix PR82357 - bogus "cannot bind bitfield" error

From: Jason Merrill <jason at redhat dot com>
To: Markus Trippelsdorf <markus at trippelsdorf dot de>
Cc: gcc-patches List <gcc-patches at gcc dot gnu dot org>
Date: Fri, 13 Oct 2017 12:02:01 -0400
Subject: Re: [PATCH C++] Fix PR82357 - bogus "cannot bind bitfield" error
Authentication-results: sourceware.org; auth=none
References: <20171013094053.GC235@x4>

On Fri, Oct 13, 2017 at 5:40 AM, Markus Trippelsdorf
<markus@trippelsdorf.de> wrote:
> r253266 introduced a bogus "cannot bind bitfield" error that breaks
> building Chromium and Node.js.
> Fix by removing the ugly goto.
>
> Tested on ppc64le.
> Ok for trunk?

No, this just undoes my change, so we go back to not doing type
checking for non-dependent static casts.  Better I think to avoid the
call to build_static_cast in the first place, by teaching
stabilize_reference that it can return a NON_DEPENDENT_EXPR unchanged.
How does this (untested) patch work for you?

Attachment: nd-ref.diff
Description: Text document

Follow-Ups:
- Re: [PATCH C++] Fix PR82357 - bogus "cannot bind bitfield" error
  - From: Markus Trippelsdorf

References:
- [PATCH C++] Fix PR82357 - bogus "cannot bind bitfield" error
  - From: Markus Trippelsdorf

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]