From: Jeff Law <jeffreyalaw@gmail.com>
To: Cupertino Miranda <cupertino.miranda@oracle.com>
Cc: jose.marchesi@oracle.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] Corrected pr25521.c target matching.
Date: Sun, 2 Apr 2023 22:16:53 -0600 [thread overview]
Message-ID: <e7553709-6ea6-d806-6e35-1b87a572aa81@gmail.com> (raw)
In-Reply-To: <878rg01ql5.fsf@oracle.com>
On 3/13/23 11:57, Cupertino Miranda wrote:
>
> Cupertino Miranda via Gcc-patches writes:
>
>>> On 1/24/23 05:24, Cupertino Miranda wrote:
>>>> Thank you for the comments and suggestions.
>>>> I have changed the patch.
>>>> Unfortunately in case of rx target I could not make
>>>> scan-assembler-symbol-section to match. I believe it is because the
>>>> .section and .global entries order is reversed in this target.
>>>> Patch in inlined below. looking forward to your comments.
>>> Sorry for the long delays. I've installed this version.
>>>
>>> As a follow-up, can you update the documentation in doc/sourcebuild.texi to
>>> include the new check-effective-target test?
>>
>> Hi Jeff,
>>
>> Thank you for installing the patch.
>> I have prepared the doc change you requested.
>> Hopefully this is what you were expecting.
>>
>> Regards,
>> Cupertino
>
> Just realized previous patch was in incorrect placement alphabetically.
> Please consider this one instead.
Installed. Thanks.
jeff
prev parent reply other threads:[~2023-04-03 4:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:52 [PATCH] `const volatile' sections selection - bugzilla #107181 Cupertino Miranda
2022-12-02 17:52 ` [PATCH 1/2] select .rodata for const volatile variables Cupertino Miranda
2022-12-05 18:06 ` Jeff Law
2022-12-07 15:12 ` Cupertino Miranda
2022-12-15 10:13 ` Cupertino Miranda
2022-12-22 17:21 ` [PING] " Cupertino Miranda
2023-01-02 10:42 ` Cupertino Miranda
2023-01-09 7:57 ` Richard Biener
2023-01-13 15:06 ` Cupertino Miranda
2023-01-19 9:59 ` Cupertino Miranda
2023-01-22 18:43 ` Jeff Law
2023-01-22 18:49 ` Jeff Law
2022-12-02 17:52 ` [PATCH 2/2] Corrected pr25521.c target matching Cupertino Miranda
2022-12-05 18:47 ` Jeff Law
2022-12-07 15:45 ` Cupertino Miranda
2022-12-15 10:14 ` Cupertino Miranda
2022-12-22 17:22 ` [PING] " Cupertino Miranda
2023-01-02 10:43 ` Cupertino Miranda
2023-01-13 15:13 ` Cupertino Miranda
2023-01-22 19:04 ` Jeff Law
2023-01-24 12:24 ` Cupertino Miranda
2023-01-31 9:10 ` [PING] " Cupertino Miranda
2023-02-07 9:53 ` Cupertino Miranda
2023-02-17 14:33 ` Cupertino Miranda
2023-02-27 10:17 ` Cupertino Miranda
2023-03-09 9:51 ` [PING, PING] " Cupertino Miranda
2023-03-11 16:25 ` Jeff Law
2023-03-13 17:52 ` Cupertino Miranda
2023-03-13 17:57 ` Cupertino Miranda
2023-04-03 4:16 ` Jeff Law [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=e7553709-6ea6-d806-6e35-1b87a572aa81@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=cupertino.miranda@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jose.marchesi@oracle.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).