public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: David Malcolm <dmalcolm@redhat.com>,
	Joseph Myers <joseph@codesourcery.com>,
	 Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	 buildbot@sourceware.org
Subject: Re: CI for "Option handling: add documentation URLs"
Date: Thu, 22 Feb 2024 11:57:50 +0800	[thread overview]
Message-ID: <CAKcpw6Xy-7wvt80bJdBWQKEwZFC1D1p7QhfMBqir2p3zpfHjHA@mail.gmail.com> (raw)
In-Reply-To: <20240218225810.GH16832@gnu.wildebeest.org>

Mark Wielaard <mark@klomp.org> 于2024年2月19日周一 06:58写道:
>
> Hi David,
>
> On Thu, Jan 04, 2024 at 09:57:09AM -0500, David Malcolm wrote:
> > I've pushed the .opt.urls patch kit to gcc trunk [1], so hopefully the
> > CI check you wrote can go live now.
>
> And then I was on vacation myself and forgot. I am sorry.
>
> So, I did try the regenerate-opt-urls locally, and it did generate the
> attached diff. Which seems to show we really need this automated.
>
> Going over the diff. The -Winfinite-recursion in rust does indeed seem
> new.  As do the -mapx-inline-asm-use-gpr32 and mevex512 for i386.  And
> the avr options -mskip-bug, -mflmap and mrodata-in-ram.  The change in
> common.opt.urls for -Wuse-after-free comes from it being moved from
> c++ to the c-family. The changes in mips.opt.urls seem to come from
> commit 46df1369 "doc/invoke: Remove duplicate explicit-relocs entry of
> MIPS".
>

For MIPS, it's due to malformed patches to invoke.text.
I will fix them.

> The changes in c.opt.urls seem mostly reordering. The sorting makes
> more sense after the diff imho. And must have come from commit
> 4666cbde5 "Sort warning options in c-family/c.opt".
>
> Also the documentation for -Warray-parameter was fixed.
>
> So I think the regenerate-opt-urls check does work as intended. So
> lets automate it, because it looks like nobody regenerated the
> url.opts after updating the documentation.
>
> But we should first apply this diff. Could you double check it is
> sane/correct?
>
> Thanks,
>
> Mark



-- 
YunQiang Su

  parent reply	other threads:[~2024-02-22  3:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231210233506.GC14917@gnu.wildebeest.org>
     [not found] ` <20231214150143.3305661-1-dmalcolm@redhat.com>
2023-12-15  0:59   ` [PATCH 0/4] v3 of: Option handling: add documentation URLs Mark Wielaard
2023-12-15 14:47     ` David Malcolm
2024-01-04 14:57     ` CI for "Option handling: add documentation URLs" David Malcolm
2024-02-18 22:58       ` Mark Wielaard
2024-02-19 11:38         ` Mark Wielaard
2024-02-22  3:57         ` YunQiang Su [this message]
2024-02-24 17:42           ` Mark Wielaard
2024-03-03 20:04             ` Mark Wielaard
2024-03-04 13:48               ` David Malcolm
2024-03-05 12:06                 ` Mark Wielaard
2024-03-05 13:34                   ` David Malcolm
2024-03-05 20:24                     ` Mark Wielaard
2024-03-15  7:33                       ` YunQiang Su
2024-03-15 10:06                         ` Mark Wielaard

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=CAKcpw6Xy-7wvt80bJdBWQKEwZFC1D1p7QhfMBqir2p3zpfHjHA@mail.gmail.com \
    --to=wzssyqa@gmail.com \
    --cc=buildbot@sourceware.org \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=mark@klomp.org \
    --cc=tobias@codesourcery.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).