From: NightStrike <nightstrike@gmail.com>
To: Jonathan Yong <10walls@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] More LLP64 fixes and __PIC__ values fixes for PE targets
Date: Sun, 26 Feb 2023 00:12:26 -0500 [thread overview]
Message-ID: <CAF1jjLvkYXvE7XnH-p-avLcVTbqSP3EAud=MH0t5o+4_+0YN1w@mail.gmail.com> (raw)
In-Reply-To: <a7b5aee2-0203-dc57-0328-e3989e7ecc8e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 123 bytes --]
On Tue, Feb 14, 2023, 05:42 Jonathan Yong via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> Attached patches OK?
Ping
next prev parent reply other threads:[~2023-02-26 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:42 Jonathan Yong
2023-02-26 5:12 ` NightStrike [this message]
2023-03-11 17:29 ` Jeff Law
2023-03-12 1:54 ` Jonathan Yong
2023-03-12 16:54 ` Jeff Law
2023-03-15 0:12 ` Jonathan Yong
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='CAF1jjLvkYXvE7XnH-p-avLcVTbqSP3EAud=MH0t5o+4_+0YN1w@mail.gmail.com' \
--to=nightstrike@gmail.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).