public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Sebor <msebor@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/13] v2 warning control by group and location (PR 74765)
Date: Sat, 17 Jul 2021 22:36:41 +0200	[thread overview]
Message-ID: <20210717203641.dywmatkfj5gwon6u@lug-owl.de> (raw)
In-Reply-To: <3a5ea83c-0d91-d123-f537-f8f1223df890@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2644 bytes --]

Hi Martin!

On Fri, 2021-06-04 15:27:04 -0600, Martin Sebor <msebor@gmail.com> wrote:
> This is a revised patch series to add warning control by group and
> location, updated based on feedback on the initial series.
[...]

My automated checking (in this case: Using Debian's "gcc-snapshot"
package) indicates that between versions 1:20210527-1 and
1:20210630-1, building GDB breaks. Your patch is a likely candidate.
It's a case where a method asks for a nonnull argument and later on
checks for NULLness again. The build log is currently available at
(http://wolf.lug-owl.de:8080/jobs/gdb-vax-linux/5), though obviously
breaks for any target:

configure --target=vax-linux --prefix=/tmp/gdb-vax-linux
make all-gdb

[...]
[all 2021-07-16 19:19:25]   CXX    compile/compile.o
[all 2021-07-16 19:19:30] In file included from ./../gdbsupport/common-defs.h:126,
[all 2021-07-16 19:19:30]                  from ./defs.h:28,
[all 2021-07-16 19:19:30]                  from compile/compile.c:20:
[all 2021-07-16 19:19:30] ./../gdbsupport/gdb_unlinker.h: In constructor 'gdb::unlinker::unlinker(const char*)':
[all 2021-07-16 19:19:30] ./../gdbsupport/gdb_assert.h:35:4: error: 'nonnull' argument 'filename' compared to NULL [-Werror=nonnull-compare]
[all 2021-07-16 19:19:30]    35 |   ((void) ((expr) ? 0 :                                                       \
[all 2021-07-16 19:19:30]       |   ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[all 2021-07-16 19:19:30]    36 |            (gdb_assert_fail (#expr, __FILE__, __LINE__, FUNCTION_NAME), 0)))
[all 2021-07-16 19:19:30]       |            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[all 2021-07-16 19:19:30] ./../gdbsupport/gdb_unlinker.h:38:5: note: in expansion of macro 'gdb_assert'
[all 2021-07-16 19:19:30]    38 |     gdb_assert (filename != NULL);
[all 2021-07-16 19:19:30]       |     ^~~~~~~~~~
[all 2021-07-16 19:19:31] cc1plus: all warnings being treated as errors
[all 2021-07-16 19:19:31] make[1]: *** [Makefile:1641: compile/compile.o] Error 1
[all 2021-07-16 19:19:31] make[1]: Leaving directory '/var/lib/laminar/run/gdb-vax-linux/5/binutils-gdb/gdb'
[all 2021-07-16 19:19:31] make: *** [Makefile:11410: all-gdb] Error 2


Code is this:

 31 class unlinker
 32 {
 33  public:
 34 
 35   unlinker (const char *filename) ATTRIBUTE_NONNULL (2)
 36     : m_filename (filename)
 37   {
 38     gdb_assert (filename != NULL);
 39   }

I'm quite undecided whether this is bad behavior of GCC or bad coding
style in Binutils/GDB, or both.

Thanks,
  Jan-Benedict

-- 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2021-07-17 20:36 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 22:02 [PATCH 0/11] " Martin Sebor
2021-05-24 22:07 ` [PATCH 1/11] introduce xxx_no_warning APIs Martin Sebor
2021-05-24 22:09   ` [PATCH 2/11] use xxx_no_warning APIs in Ada Martin Sebor
2021-05-25  8:59     ` Eric Botcazou
2021-05-27 20:29       ` Martin Sebor
2021-05-24 22:10   ` [PATCH 3/11] use xxx_no_warning APIs in C Martin Sebor
2021-05-24 22:11   ` [PATCH 4/11] use xxx_no_warning APIs in C family Martin Sebor
2021-05-24 22:11   ` [PATCH 5/11] use xxx_no_warning APIs in C++ Martin Sebor
2021-05-24 22:12   ` [PATCH 6/11] use xxx_no_warning APIs in Fortran Martin Sebor
2021-05-24 22:13   ` [PATCH 7/11] " Martin Sebor
2021-05-24 22:14   ` [PATCH 8/11] use xxx_no_warning APIs in Objective-C Martin Sebor
2021-05-25 14:01     ` Iain Sandoe
2021-05-25 15:48       ` Martin Sebor
2021-05-25 15:56         ` Iain Sandoe
2021-05-24 22:15   ` [PATCH 9/11] use xxx_no_warning APIs in rl78 back end Martin Sebor
2021-05-24 22:16   ` [PATCH 10/11] use xxx_no_warning APIs in libcc1 Martin Sebor
2021-05-24 22:16   ` [PATCH 11/11] use xxx_no_warning APIs in the middle end Martin Sebor
2021-05-24 23:08     ` David Malcolm
2021-05-25  0:44       ` Martin Sebor
2021-05-24 23:08 ` [PATCH 0/11] warning control by group and location (PR 74765) David Malcolm
2021-05-25  0:42   ` Martin Sebor
2021-05-25  9:04     ` Richard Biener
2021-05-25 20:50       ` Martin Sebor
2021-05-27 11:19     ` Richard Sandiford
2021-05-27 16:41       ` Martin Sebor
2021-05-27 21:55         ` David Malcolm
2021-05-28  4:40           ` Jason Merrill
2021-06-04 21:27   ` [PATCH 0/13] v2 " Martin Sebor
2021-06-04 21:41     ` [PATCH 1/13] v2 [PATCH 1/13] Add support for per-location warning groups " Martin Sebor
2021-06-21 21:34       ` [PING][PATCH " Martin Sebor
2021-06-22 23:18       ` [PATCH " David Malcolm
2021-06-22 23:28         ` David Malcolm
2021-06-23 19:47           ` Martin Sebor
2021-06-24  5:26             ` Jeff Law
2021-06-25  1:34               ` Martin Sebor
2021-09-01 19:35             ` Thomas Schwinge
2021-09-02  0:14               ` Martin Sebor
2021-09-03 19:16                 ` Thomas Schwinge
2021-09-10  7:45                   ` [PING] Don't maintain a warning spec for 'UNKNOWN_LOCATION'/'BUILTINS_LOCATION' [PR101574] (was: [PATCH 1/13] v2 [PATCH 1/13] Add support for per-location warning groups (PR 74765)) Thomas Schwinge
2021-09-13 14:00                     ` Jeff Law
2021-11-09 14:18                   ` Use 'location_hash' for 'gcc/diagnostic-spec.h:nowarn_map' " Thomas Schwinge
2021-11-15 15:01                     ` [ping] Use 'location_hash' for 'gcc/diagnostic-spec.h:nowarn_map' Thomas Schwinge
2021-11-15 16:43                       ` Martin Sebor
2021-11-09 10:28                 ` Get rid of infinite recursion for 'typedef' used with GTY-marked 'gcc/diagnostic-spec.h:nowarn_map' [PR101204] (was: [PATCH 1/13] v2 [PATCH 1/13] Add support for per-location warning groups (PR 74765)) Thomas Schwinge
2021-11-09 10:54                   ` Richard Biener
2021-11-09 12:25                     ` Get rid of infinite recursion for 'typedef' used with GTY-marked 'gcc/diagnostic-spec.h:nowarn_map' [PR101204, PR103157] Thomas Schwinge
2021-11-10  4:52                   ` Get rid of infinite recursion for 'typedef' used with GTY-marked 'gcc/diagnostic-spec.h:nowarn_map' [PR101204] Martin Sebor
2021-11-24 10:28                     ` 'gengtype' (was: Get rid of infinite recursion for 'typedef' used with GTY-marked 'gcc/diagnostic-spec.h:nowarn_map' [PR101204]) Thomas Schwinge
2021-06-04 21:41     ` [PATCH 2/13] v2 Use new per-location warning APIs in Ada Martin Sebor
2021-06-24  5:07       ` Jeff Law
2021-06-28 21:20         ` Martin Sebor
2021-06-04 21:41     ` [PATCH 3/13] v2 Use new per-location warning APIs in C front end Martin Sebor
2021-06-21 21:35       ` [PING][PATCH " Martin Sebor
2021-06-24  5:09       ` [PATCH " Jeff Law
2021-06-25  1:35         ` Martin Sebor
2021-06-04 21:42     ` [PATCH 4/13] v2 Use new per-location warning APIs in C family code Martin Sebor
2021-06-21 21:35       ` [PING][PATCH " Martin Sebor
2021-06-24  5:06       ` [PATCH " Jeff Law
2021-06-25  1:36         ` Martin Sebor
2021-06-04 21:42     ` [PATCH 5/13] v2 Use new per-location warning APIs in the RL78 back end Martin Sebor
2021-06-24  5:06       ` Jeff Law
2021-06-04 21:42     ` [PATCH 6/13] v2 Use new per-location warning APIs in the C++ front end Martin Sebor
2021-06-21 21:37       ` [PING][PATCH " Martin Sebor
2021-06-24  5:12       ` [PATCH " Jeff Law
2021-06-25  1:38         ` Martin Sebor
2021-06-04 21:42     ` [PATCH 7/13] v2 Use new per-location warning APIs in the FORTRAN " Martin Sebor
2021-06-21 21:42       ` [PING][PATCH " Martin Sebor
2021-06-24  5:05       ` [PATCH " Jeff Law
2021-06-28 21:21         ` Martin Sebor
2021-06-04 21:42     ` [PATCH 8/13] v2 Use new per-location warning APIs in libcc1 Martin Sebor
2021-06-24  5:04       ` Jeff Law
2021-06-28 21:22         ` Martin Sebor
2021-06-04 21:43     ` [PATCH 9/13] v2 Use new per-location warning APIs in LTO Martin Sebor
2021-06-21 21:54       ` [PING][PATCH " Martin Sebor
2021-06-24  9:32         ` Richard Biener
2021-06-24 15:27           ` Martin Sebor
2021-06-25  7:46             ` Richard Biener
2021-06-24  5:03       ` [PATCH " Jeff Law
2021-06-04 21:43     ` [PATCH 10/13] v2 Use new per-location warning APIs in the middle end Martin Sebor
2021-06-21 21:58       ` [PING][PATCH " Martin Sebor
2021-06-24  5:15       ` [PATCH " Jeff Law
2021-06-25  1:40         ` Martin Sebor
2021-06-04 21:43     ` [PATCH 11/13] v2 Use new per-location warning APIs in the Objective-C front end Martin Sebor
2021-06-24  5:02       ` Jeff Law
2021-06-28 21:22         ` Martin Sebor
2021-06-04 21:43     ` [PATCH 12/13] v2 Remove TREE_NO_WARNING and gimple*no_warning* APIs Martin Sebor
2021-06-24  5:01       ` Jeff Law
2021-06-04 21:43     ` [PATCH 13/13] v2 Add regression tests for PR 74765 and 74762 Martin Sebor
2021-06-24  4:56       ` Jeff Law
2021-06-28 21:23         ` Martin Sebor
2021-06-15  1:29     ` [PING][PATCH 0/13] v2 warning control by group and location (PR 74765) Martin Sebor
2021-07-17 20:36     ` Jan-Benedict Glaw [this message]
2021-07-19 15:08       ` [PATCH " Martin Sebor
2021-07-28 11:14         ` Andrew Burgess
2021-07-28 16:16           ` Martin Sebor
2021-07-29  8:26             ` Andrew Burgess
2021-07-29 14:41               ` Martin Sebor
2021-05-30  2:06 ` [PATCH 0/11] " Jeff Law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210717203641.dywmatkfj5gwon6u@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=msebor@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).