From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jonathan Yong <10walls@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] gcc.c-torture/compile/103818.c: enable for llp64 too
Date: Mon, 27 Feb 2023 21:10:52 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2302272107230.10325@arjuna.pair.com> (raw)
In-Reply-To: <f4ec9808-7f52-659f-7859-72573bb76263@gmail.com>
On Sun, 26 Feb 2023, Jonathan Yong via Gcc-patches wrote:
> Patch OK for master branch? I did not see any obvious issues to exclude LLP64
> specifically.
I see "lp64 || lp64" in that patch (which should preferably have
been sent inline, as it's harder to quote an attached patch,
QED). Sending the wrong version? Don't forget to test it.
brgds, H-P
next prev parent reply other threads:[~2023-02-28 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 6:38 Jonathan Yong
2023-02-28 2:10 ` Hans-Peter Nilsson [this message]
2023-02-28 7:23 ` Jonathan Yong
2023-03-11 16:18 ` Jeff Law
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=alpine.BSF.2.20.16.2302272107230.10325@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=10walls@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).