On Tue, Mar 01, 2016 at 08:08:03PM +0100, Marek Polacek wrote:
> On Tue, Mar 01, 2016 at 09:31:26AM -0700, Jeff Law wrote:
> > On 02/24/2016 09:31 AM, Marek Polacek wrote:
> > >The following is another issue with macros from system headers. In this
> > >case
> > >bool is defined in a system heade
On Tue, Mar 01, 2016 at 09:31:26AM -0700, Jeff Law wrote:
> On 02/24/2016 09:31 AM, Marek Polacek wrote:
> >The following is another issue with macros from system headers. In this case
> >bool is defined in a system header to expand to _Bool and the "is promoted
> >to"
> >warning didn't trigger b
On 02/24/2016 09:31 AM, Marek Polacek wrote:
The following is another issue with macros from system headers. In this case
bool is defined in a system header to expand to _Bool and the "is promoted to"
warning didn't trigger because of that. The fix is to use the expanded
location.
Bootstrappe
Ping.
On Wed, Feb 24, 2016 at 05:31:22PM +0100, Marek Polacek wrote:
> The following is another issue with macros from system headers. In this case
> bool is defined in a system header to expand to _Bool and the "is promoted to"
> warning didn't trigger because of that. The fix is to use the exp
The following is another issue with macros from system headers. In this case
bool is defined in a system header to expand to _Bool and the "is promoted to"
warning didn't trigger because of that. The fix is to use the expanded
location.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
201
