From: Sam James <sam@gentoo.org>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Add dg-do run to even more tests, fix typo
Date: Fri, 26 Jul 2024 18:44:34 +0100 [thread overview]
Message-ID: <8734nwhwu5.fsf@gentoo.org> (raw)
In-Reply-To: <5cad85cc16ef3e15b73bcabbf8a6834954443566.1721349366.git.sam@gentoo.org> (Sam James's message of "Fri, 19 Jul 2024 01:36:06 +0100")
Sam James <sam@gentoo.org> writes:
> All of these are for wrong-code bugs. Confirmed to be used before but
> with no execution.
>
> Tested on x86_64-pc-linux-gnu and checked test logs before/after.
>
Pushed as obvious after discussion on IRC. Thanks.
prev parent reply other threads:[~2024-07-26 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 0:36 Sam James
2024-07-26 17:44 ` Sam James [this message]
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=8734nwhwu5.fsf@gentoo.org \
--to=sam@gentoo.org \
--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).