public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Mark Wielaard <mark@klomp.org>, YunQiang Su <wzssyqa@gmail.com>
Cc: 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: Mon, 04 Mar 2024 08:48:49 -0500	[thread overview]
Message-ID: <bc5050aa94401c95f3716b592f7f30ebf5d5349b.camel@redhat.com> (raw)
In-Reply-To: <20240303200447.GJ13156@gnu.wildebeest.org>

On Sun, 2024-03-03 at 21:04 +0100, Mark Wielaard wrote:
> Hi,
> 
> On Sat, Feb 24, 2024 at 06:42:58PM +0100, Mark Wielaard wrote:
> > On Thu, Feb 22, 2024 at 11:57:50AM +0800, YunQiang Su wrote:
> > > Mark Wielaard <mark@klomp.org> 于2024年2月19日周一 06:58写道:
> > > > 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.
> > 
> > Thanks. So with your commit 00bc8c0998d8 ("invoke.texi: Fix some
> > skipping UrlSuffix problem for MIPS") pushed now, the attached
> > patch
> > fixes the remaining issues.
> > 
> > Is this OK to push?

Thanks, looks good to me.

> Ping.
> 
> I have now regenerated the patch to also include the new avr mfuse-
> add
> change. It would be nice to get this committed so we can turn on the
> automatic checker.

Please go ahead with that.

Thanks
Dave


  reply	other threads:[~2024-03-04 13:48 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
2024-02-24 17:42           ` Mark Wielaard
2024-03-03 20:04             ` Mark Wielaard
2024-03-04 13:48               ` David Malcolm [this message]
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=bc5050aa94401c95f3716b592f7f30ebf5d5349b.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=buildbot@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=mark@klomp.org \
    --cc=tobias@codesourcery.com \
    --cc=wzssyqa@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).