public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Matthieu Longo <matthieu.longo@arm.com>,
	Nick Clifton <nickc@redhat.com>, Alan Modra <amodra@gmail.com>
Cc: Richard Earnshaw <richard.earnshaw@arm.com>, binutils@sourceware.org
Subject: Re: [PATCH v1 2/3] gas: add new command line options to control diagnostic information messages
Date: Wed, 3 Jul 2024 09:55:38 +0200	[thread overview]
Message-ID: <b7e97af9-d8f7-4c6f-b936-b58e6be8daad@suse.com> (raw)
In-Reply-To: <20240702174003.1424939-3-matthieu.longo@arm.com>

On 02.07.2024 19:40, Matthieu Longo wrote:
> 
> gas currently emits information messages for context information along warnings.
> In the context of system register tests in AArch64 backend, these messages
> pollute the tests when checking for error message patterns in stderr output.
> 
> This patch aims at providing two new flags while preserving the existing
> behavior if none of the options is provided.
>   * --info, similar to the existing --warn flag to enable diagnostic
>     information messages (default behavior).
>   * --no-info, similar to the existing --no-warn flag to disable diagnostic
>     information messages.

Nick, Alan, what is your take on these option names? Having dropped the 's'
from the original form is an improvement imo, but I'm a little afraid "info"
(unlike "warn") may become ambiguous with something else down the road.

> It also adds the flags to the existing documentation, and command manual.

In all of the doc changes you appear to be entirely ignoring the present
alphabetical sorting in the blocks you insert into. The info additions
want to all move further up; the sorting there isn't on a "related to one
another" basis afaics.

> ---
>  gas/as.c                | 18 +++++++++++++++++-
>  gas/as.h                |  3 +++
>  gas/config/tc-aarch64.c |  3 +++

This change will need explicit buy-off by Arm64 folks. Mind me asking why
you Cc-ed only Richard, but not Marcus?

Jan

>  gas/doc/as.texi         | 34 ++++++++++++++++++++++++++++++++++
>  gas/messages.c          |  3 +++
>  5 files changed, 60 insertions(+), 1 deletion(-)
> 


  reply	other threads:[~2024-07-03  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 17:40 [PATCH v1 0/3] gas: add command line option to inhibit info messages Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 1/3] gas: minor reformatting in command line help and doc Matthieu Longo
2024-07-03  7:44   ` Jan Beulich
2024-07-18 16:05     ` Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 2/3] gas: add new command line options to control diagnostic information messages Matthieu Longo
2024-07-03  7:55   ` Jan Beulich [this message]
2024-07-03 16:52     ` Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 3/3] aarch64: testsuite: remove macro expansion messages from expected error output Matthieu Longo

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=b7e97af9-d8f7-4c6f-b936-b58e6be8daad@suse.com \
    --to=jbeulich@suse.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=matthieu.longo@arm.com \
    --cc=nickc@redhat.com \
    --cc=richard.earnshaw@arm.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).