Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread Martin Sebor
On 12/14/2017 06:53 PM, David Malcolm wrote: On Thu, 2017-12-14 at 16:07 -0700, Martin Sebor wrote: On 12/14/2017 12:24 PM, Jeff Law wrote: On 12/11/2017 03:18 PM, Martin Sebor wrote: On 12/11/2017 02:08 PM, David Malcolm wrote: On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: Bug 8336

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread David Malcolm
On Thu, 2017-12-14 at 16:07 -0700, Martin Sebor wrote: > On 12/14/2017 12:24 PM, Jeff Law wrote: > > On 12/11/2017 03:18 PM, Martin Sebor wrote: > > > On 12/11/2017 02:08 PM, David Malcolm wrote: > > > > On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: > > > > > Bug 83369 - Missing diagnostic

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread Martin Sebor
On 12/14/2017 12:24 PM, Jeff Law wrote: On 12/11/2017 03:18 PM, Martin Sebor wrote: On 12/11/2017 02:08 PM, David Malcolm wrote: On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is issued for an inlined call to a

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread Jeff Law
On 12/11/2017 09:51 AM, Martin Sebor wrote: > Bug 83369 - Missing diagnostics during inlining, notes that when > -Wnonnull is issued for an inlined call to a built-in function, > GCC doesn't print the inlining stack, making it hard to debug > where the problem comes from. > > When the -Wnonnull wa

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread Jeff Law
On 12/11/2017 06:16 PM, David Malcolm wrote: > On Mon, 2017-12-11 at 15:18 -0700, Martin Sebor wrote: >> On 12/11/2017 02:08 PM, David Malcolm wrote: >>> On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is is

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-14 Thread Jeff Law
On 12/11/2017 03:18 PM, Martin Sebor wrote: > On 12/11/2017 02:08 PM, David Malcolm wrote: >> On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: >>> Bug 83369 - Missing diagnostics during inlining, notes that when >>> -Wnonnull is issued for an inlined call to a built-in function, >>> GCC doesn

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-11 Thread David Malcolm
On Mon, 2017-12-11 at 15:18 -0700, Martin Sebor wrote: > On 12/11/2017 02:08 PM, David Malcolm wrote: > > On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: > > > Bug 83369 - Missing diagnostics during inlining, notes that when > > > -Wnonnull is issued for an inlined call to a built-in functio

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-11 Thread Martin Sebor
On 12/11/2017 02:08 PM, David Malcolm wrote: On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is issued for an inlined call to a built-in function, GCC doesn't print the inlining stack, making it hard to debug where

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-11 Thread David Malcolm
On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: > Bug 83369 - Missing diagnostics during inlining, notes that when > -Wnonnull is issued for an inlined call to a built-in function, > GCC doesn't print the inlining stack, making it hard to debug > where the problem comes from. > > When the -

[PATCH] have -Wnonnull print inlining stack (PR 83369)

2017-12-11 Thread Martin Sebor
Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is issued for an inlined call to a built-in function, GCC doesn't print the inlining stack, making it hard to debug where the problem comes from. When the -Wnonnull warning was introduced into the middle-end the diagnostic