From: Jeff Law <law@redhat.com>
To: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] Implement TARGET_HANDLE_GENERIC_ATTRIBUTE
Date: Tue, 03 Sep 2019 21:17:00 -0000 [thread overview]
Message-ID: <9656bb7e-73a7-28d1-e4b6-a2ec30c83458@redhat.com> (raw)
In-Reply-To: <20190903220029.411e45a4@jozef-kubuntu>
On 9/3/19 3:00 PM, Jozef Lawrynowicz wrote:
> On Tue, 3 Sep 2019 13:37:57 -0600
> Jeff Law <law@redhat.com> wrote:
>
>> On 8/30/19 4:09 AM, Jozef Lawrynowicz wrote:
>>> The attached patch adds a new target hook "TARGET_HANDLE_GENERIC_ATTRIBUTE"
>>> which enables a back end to perform additional processing of an attribute that
>>> is normally handled by a front end.
>>>
>>> So far only the "section" and "noinit" attribute make use of this hook, as the
>>> msp430 back end requires additional attribute conflict checking to be performed
>>> on these generic attributes.
>>>
>>>
>>> 0001-Implement-TARGET_HANDLE_GENERIC_ATTRIBUTE.patch
>>>
>>> From e693da709114df378e2ea8b1d3729b105c99a495 Mon Sep 17 00:00:00 2001
>>> From: Jozef Lawrynowicz <jozef.l@mittosystems.com>
>>> Date: Wed, 28 Aug 2019 14:09:20 +0100
>>> Subject: [PATCH 1/3] Implement TARGET_HANDLE_GENERIC_ATTRIBUTE
>>>
>>> gcc/ChangeLog:
>>>
>>> 2019-08-29 Jozef Lawrynowicz <jozef.l@mittosystems.com>
>>>
>>> * config/msp430/msp430.c (TARGET_HANDLE_GENERIC_ATTRIBUTE): Define.
>>> (msp430_handle_generic_attribute): New function.
>>> * doc/tm.texi: Regenerate.
>>> * doc/tm.texi.in: Add TARGET_HANDLE_GENERIC_ATTRIBUTE.
>>> * hooks.c (hook_tree_treeptr_tree_tree_int_boolptr_null): New.
>>> * hooks.h (hook_tree_treeptr_tree_tree_int_boolptr_null): New.
>>> * target.def: Define new hook TARGET_HANDLE_GENERIC_ATTRIBUTE.
>>>
>>> gcc/c-family/ChangeLog:
>>>
>>> 2019-08-29 Jozef Lawrynowicz <jozef.l@mittosystems.com>
>>>
>>> * c-attribs.c (handle_section_attribute): Call the
>>> handle_generic_attribute target hook after performing target
>>> independent processing.
>>> (handle_noinit_attribute): Likewise.
>> Just a nit. In a couple places in c-attribs.c you have:
>>
>>> + if (!(* no_add_attrs))
>>
>> Drop the whitespace between the * and no_add_attrs.
>>
>> OK with that change.
>
> Thanks, I fixed that and other instances of "* <varname>" in the patches
> before applying. Seems to be a common style slip-up in the msp430 backend.
Yea, saw it's relatively common in the msp430 target files, given how
often it shows up in there I didn't call it out in the msp target files
in your patch, just in the generic bits.
Jeff
next prev parent reply other threads:[~2019-09-03 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 10:18 [PATCH 0/3] MSP430: Improve attribute handling Jozef Lawrynowicz
2019-08-30 10:36 ` [PATCH 1/3] Implement TARGET_HANDLE_GENERIC_ATTRIBUTE Jozef Lawrynowicz
2019-09-03 19:38 ` Jeff Law
2019-09-03 21:00 ` Jozef Lawrynowicz
2019-09-03 21:17 ` Jeff Law [this message]
2019-08-30 10:45 ` [PATCH 2/3][MSP430] Setup exclusion tables for function and data attributes Jozef Lawrynowicz
2019-09-03 19:39 ` Jeff Law
2019-08-30 10:58 ` [PATCH 3/3][MSP430] Use default_elf_select_section to select sections for data where possible Jozef Lawrynowicz
2019-09-03 19:40 ` 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=9656bb7e-73a7-28d1-e4b6-a2ec30c83458@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jozef.l@mittosystems.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).