public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: bugaevc@gmail.com
Cc: gcc-patches@gcc.gnu.org, bug-hurd@gnu.org
Subject: Re: [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64)
Date: Tue, 09 Apr 2024 17:04:59 -0700 (PDT)	[thread overview]
Message-ID: <mhng-e6f1afa8-9a28-46a0-a90c-a0f1b4e34480@palmer-ri-x1c9a> (raw)
In-Reply-To: <CAN9u=Hf5d9n1TL_k1OTvHDHwMBk+Z06yO1qa52FroYSUkbn6+w@mail.gmail.com>

On Tue, 09 Apr 2024 09:57:11 PDT (-0700), bugaevc@gmail.com wrote:
> On Tue, Apr 9, 2024 at 7:24 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>> > I assume the buildbot failure that I just got an email about is
>> > unrelated; it's failing on some RISC-V thing.
>>
>> Sorry if I missed something here, do you have a pointer?
>
> The buildbot failure emails reference [0] and [1].
>
> [0]: https://builder.sourceware.org/buildbot/#/builders/269/builds/4216
> [1]: https://builder.sourceware.org/buildbot/#/builders/269/builds/4218
>
>  Specifically, the "git diff_1" step seems to be failing with
>
>     diff --git a/gcc/config/riscv/riscv.opt.urls
> b/gcc/config/riscv/riscv.opt.urls
>     index da31820e234..351f7f0dda2 100644
>     --- a/gcc/config/riscv/riscv.opt.urls
>     +++ b/gcc/config/riscv/riscv.opt.urls
>     @@ -89,3 +89,5 @@ UrlSuffix(gcc/RISC-V-Options.html#index-minline-strncmp)
>      minline-strlen
>      UrlSuffix(gcc/RISC-V-Options.html#index-minline-strlen)
>
>     +; skipping UrlSuffix for 'mtls-dialect=' due to finding no URLs
>     +
>
> I don't know what to make of that, but it seems unrelated to my
> aarch64-gnu changes.

I'd never heard of it either, looks like a new thing we're supposed to 
do when toching the options.  I just sent 
<https://inbox.sourceware.org/gcc-patches/20240410000338.3926-1-palmer@rivosinc.com/>, 
I'm sure there's a better way to do it...

>
> Sergey

  reply	other threads:[~2024-04-10  0:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 11:53 [PATCH gcc 1/3] Move GNU/Hurd startfile spec from config/i386/gnu.h to config/gnu.h Sergey Bugaev
2024-01-01 11:53 ` [PATCH gcc 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev
2024-01-01 11:53 ` [PATCH gcc 3/3] libgcc: Add basic " Sergey Bugaev
2024-01-03  9:49 ` [PATCH gcc 1/3] Move GNU/Hurd startfile spec from config/i386/gnu.h to config/gnu.h Richard Sandiford
2024-03-20 19:20   ` Thomas Schwinge
2024-03-23 14:38     ` Sergey Bugaev
2024-03-23 14:35 ` [PATCH v2 " Sergey Bugaev
2024-03-23 14:35   ` [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev
2024-04-02 17:26     ` Richard Sandiford
2024-04-05 12:13       ` Sergey Bugaev
2024-04-09  7:27         ` Thomas Schwinge
2024-04-09  8:04           ` Sergey Bugaev
2024-04-09 16:24             ` Palmer Dabbelt
2024-04-09 16:57               ` Sergey Bugaev
2024-04-10  0:04                 ` Palmer Dabbelt [this message]
2024-04-10  7:12               ` Regeneration of 'gcc/config/riscv/riscv.opt.urls' (was: [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64)) Thomas Schwinge
2024-03-23 14:35   ` [PATCH v2 3/3] libgcc: Add basic support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev

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=mhng-e6f1afa8-9a28-46a0-a90c-a0f1b4e34480@palmer-ri-x1c9a \
    --to=palmer@dabbelt.com \
    --cc=bug-hurd@gnu.org \
    --cc=bugaevc@gmail.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).