Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Sat Feb  9 02:05:37 UTC 2013 in -D 2013-02-09-gmt
Date: Sat, 09 Feb 2013 09:01:00 -0000	[thread overview]
Message-ID: <001501ce06a3$ed646a60$c82d3f20$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20130209020537.GA20140@sourceware.org>

0a1,10
> gdb/aarch64-linux-nat.c:146: code: long long: Do not use 'long long',
instead use LONGEST
gdb/aarch64-linux-nat.c:146:typedef unsigned long long dr_changed_t;
> gdb/aarch64-linux-nat.c:338: code: %ll: Do not use printf(%ll), instead
use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:338:			  "\tpid%d,
dr_changed_bp=0x%llx, "
> gdb/aarch64-linux-nat.c:339: code: %ll: Do not use printf(%ll), instead
use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:339:			  "dr_changed_wp=0x%llx\n",
> gdb/aarch64-linux-nat.c:364: code: %ll: Do not use printf(%ll), instead
use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:364:			  "\tOn exit:\n\tpid%d,
dr_changed_bp=0x%llx, "
> gdb/aarch64-linux-nat.c:365: code: %ll: Do not use printf(%ll), instead
use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:365:			  "dr_changed_wp=0x%llx\n",

  I already proposed once to add a distinction between native files,
for which I would suppress those kind of warnings.

> gdb/aarch64-linux-nat.c:736: gettext: _ markup: All messages should be
marked up with _.
gdb/aarch64-linux-nat.c:736:	  warning ("Unexpected number of hardware
watchpoint registers reported"
> gdb/aarch64-linux-nat.c:744: gettext: _ markup: All messages should be
marked up with _.
gdb/aarch64-linux-nat.c:744:      warning ("Unable to determine the number
of hardware watchpoints"
> gdb/aarch64-linux-nat.c:756: gettext: _ markup: All messages should be
marked up with _.
gdb/aarch64-linux-nat.c:756:	  warning ("Unexpected number of hardware
breakpoint registers reported"
> gdb/aarch64-linux-nat.c:764: gettext: _ markup: All messages should be
marked up with _.
gdb/aarch64-linux-nat.c:764:      warning ("Unable to determine the number
of hardware breakpoints"

  Those _("..") should indeed be added.

> gdb/aarch64-linux-tdep.c:39: comment: GNU/Linux: Do not use 'Linux',
instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly
differentiate between the two (this test assumes that word 'Linux' appears
on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/aarch64-linux-tdep.c:39:   and PSTATE registers, as defined in the
AArch64 port of the Linux

  This is a clear case on false warning,
as the word 'kernel' appears just at the next line....

  I suspect that we should merge the whole comment into a single line before

applying this rule (and probably others related to comments...


Pierre Muller
as ARI maintainer.


      reply	other threads:[~2013-02-09  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09  2:06 GDB Administrator
2013-02-09  9:01 ` Pierre Muller [this message]

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='001501ce06a3$ed646a60$c82d3f20$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    /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