From: Thomas Schwinge <tschwinge@baylibre.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, Sergey Bugaev <bugaevc@gmail.com>
Cc: gcc-patches@gcc.gnu.org, bug-hurd@gnu.org,
richard.sandiford@arm.com,
Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
Subject: Regeneration of 'gcc/config/riscv/riscv.opt.urls' (was: [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64))
Date: Wed, 10 Apr 2024 09:12:51 +0200 [thread overview]
Message-ID: <87pluxn11o.fsf@euler.schwinge.ddns.net> (raw)
In-Reply-To: <mhng-84a7f157-2d4b-47a3-a47b-4b696c3c30b4@palmer-ri-x1c9a>
Hi!
On 2024-04-09T09:24:29-0700, Palmer Dabbelt <palmer@dabbelt.com> wrote:
> On Tue, 09 Apr 2024 01:04:34 PDT (-0700), bugaevc@gmail.com wrote:
>> On Tue, Apr 9, 2024 at 10:27 AM Thomas Schwinge <tschwinge@baylibre.com> wrote:
>>> Thanks, pushed to trunk branch:
>>>
>>> - commit 532c57f8c3a15b109a46d3e2b14d60a5c40979d5 "Move GNU/Hurd startfile spec from config/i386/gnu.h to config/gnu.h"
>>> - commit 9670a2326333caa8482377c00beb65723b7b4b26 "aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64)"
>>> - commit 46c91665f4bceba19aed56f5bd6e934c548b84ff "libgcc: Add basic support for aarch64-gnu (GNU/Hurd on AArch64)"
>>
>> \o/ Thanks a lot!
>>
>> This will unblock merging the aarch64-gnu glibc port upstream.
\o/
>> 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?
<https://inbox.sourceware.org/20240409074850.ED7BD385841C@sourceware.org>
and several more such messages, requesting:
--- 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
+
To be fixed by
<https://inbox.sourceware.org/20240409145724.9640-1-ishitatsuyuki@gmail.com>
"Regenerate opt.urls".
Grüße
Thomas
next prev parent reply other threads:[~2024-04-10 7:12 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
2024-04-10 7:12 ` Thomas Schwinge [this message]
2024-03-23 14:35 ` [PATCH v2 3/3] libgcc: Add basic " 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=87pluxn11o.fsf@euler.schwinge.ddns.net \
--to=tschwinge@baylibre.com \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ishitatsuyuki@gmail.com \
--cc=palmer@dabbelt.com \
--cc=richard.sandiford@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).