From: Jeff Law <jeffreyalaw@gmail.com>
To: Jonathan Yong <10walls@gmail.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>,
NightStrike <nightstrike@gmail.com>
Subject: Re: [Patch] More LLP64 fixes and __PIC__ values fixes for PE targets
Date: Sun, 12 Mar 2023 10:54:30 -0600 [thread overview]
Message-ID: <13cd2402-9f9b-ca18-ec4c-49f038b2797d@gmail.com> (raw)
In-Reply-To: <e1983014-d3e9-b134-42bf-a114d34f96b8@gmail.com>
On 3/11/23 18:54, Jonathan Yong wrote:
> On 3/11/23 17:29, Jeff Law wrote:
>>
>>
>> On 2/14/23 03:42, Jonathan Yong via Gcc-patches wrote:
>>> Attached patches OK?
>>>
>>> 0002-gcc-testsuite-gcc.dg-fix-pic-test-case-for-PE-target.patch
>>>
>>> From 616e43ac41879040e73a266065874148553cddcc Mon Sep 17 00:00:00 2001
>>> From: Jonathan Yong<10walls@gmail.com>
>>> Date: Tue, 14 Feb 2023 10:37:03 +0000
>>> Subject: [PATCH 2/2] gcc/testsuite/gcc.dg: fix pic test case for PE
>>> targets
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>> * pic-2.c: fix expected __PIC__ value.
>>> * pic-3.c: ditto.
>>> * pic-4.c: ditto.
>> Please adjust your ChangeLog entries slightly, in particular, please
>> capitalize the first letter in each ChangeLog entry. ie, fix->Fix,
>> ditto->Ditto.
>>
>> Presumably the windows platforms are not always PIC and thus should
>> not be handled in a manner similar to MIPS?
>>
>> Assuming that's the case, then this patch is OK with the trivial
>> ChangeLog fixes.
>>
>>
>
> Windows code is effectively always PIC, since the PE loader can relocate
> it anywhere if the preferred address is already occupied. Patch still OK?
Yes, still OK. Just make the trivial ChangeLog adjustments.
Thanks,
jeff
next prev parent reply other threads:[~2023-03-12 16:54 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
2023-03-11 17:29 ` Jeff Law
2023-03-12 1:54 ` Jonathan Yong
2023-03-12 16:54 ` Jeff Law [this message]
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=13cd2402-9f9b-ca18-ec4c-49f038b2797d@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.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).