From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: ping x2 [PATCH 0/5] MSP430: Implement macros to describe relative costs of operations
Date: Fri, 6 Nov 2020 13:53:19 -0700 [thread overview]
Message-ID: <9ae3290e-c76f-f756-fba6-74c59952da14@redhat.com> (raw)
In-Reply-To: <20200915203022.6lf3pkkaj5ojybmi@jozef-acer-manjaro>
On 9/15/20 2:30 PM, Jozef Lawrynowicz wrote:
> Ping x2 for below.
>
> On Fri, Aug 07, 2020 at 12:02:59PM +0100, Jozef Lawrynowicz wrote:
>> Pinging for this series of patches.
>> Attached all patches to this mail with the ammended patch 4 thanks to
>> Segher's review.
>>
>> Thanks,
>> Jozef
>>
>> On Thu, Jul 23, 2020 at 04:43:56PM +0100, Jozef Lawrynowicz wrote:
>>> The following series of patches for MSP430 implement some of the target
>>> macros used to determine the relative costs of operations.
>>>
>>> To give an indication of the overall effect of these changes on
>>> codesize, below are some size statistics collected from all the
>>> executable files from execute.exp that are built at -Os.
>>> There are around 1470 such tests (depending on the configuration).
>>>
>>> The percentage change (((new - old)/old) * 100) in text size is calculated
>>> for each test and the given metric is applied to that overall set of data.
>>>
>>> Configuration | Mean (%) | Median (%) | Delta < 0 (count) | Delta > 0 (count)
>>> -----------------------------------------------------------------------------
>>> -mcpu=msp430 | -2.4 | -2.7 | 1454 | 17
>>> -mcpu=msp430x | -2.3 | -2.4 | 1460 | 10
>>> -mlarge | -1.7 | -1.9 | 1412 | 37
>>>
>>> Successfully regtested on trunk for msp430-elf, ok to apply?
>>>
>>> Jozef Lawrynowicz (5):
>>> MSP430: Implement TARGET_MEMORY_MOVE_COST
>>> MSP430: Implement TARGET_RTX_COSTS
>>> MSP430: Add defaulting to the insn length attribute
>>> MSP430: Implement TARGET_INSN_COST
>>> MSP430: Skip index-1.c test
>>>
>>> gcc/config/msp430/msp430-protos.h | 5 +-
>>> gcc/config/msp430/msp430.c | 867 ++++++++++++++++--
>>> gcc/config/msp430/msp430.h | 13 +
>>> gcc/config/msp430/msp430.md | 439 +++++++--
>>> gcc/config/msp430/msp430.opt | 4 +
>>> gcc/config/msp430/predicates.md | 13 +
>>> gcc/testsuite/gcc.c-torture/execute/index-1.c | 2 +
>>> 7 files changed, 1206 insertions(+), 137 deletions(-)
[ ... ]
So it's a series of 5 patches. They LGTM.   And if there's minor
updates needed to address issues found once they're on the trunk, the
consider those updates pre-approved.
Note that defining LOGICAL_OP_NON_SHORT_CIRCUIT and BRANCH_COST impact
gimple code generation. I'm a bit surprised there wasn't more fallout
in the existing tests.
jeff
next prev parent reply other threads:[~2020-11-06 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 15:43 Jozef Lawrynowicz
2020-07-23 15:47 ` [PATCH 1/5] MSP430: Implement TARGET_MEMORY_MOVE_COST Jozef Lawrynowicz
2020-07-23 15:49 ` [PATCH 2/5] MSP430: Implement TARGET_RTX_COSTS Jozef Lawrynowicz
2020-07-23 15:54 ` [PATCH 3/5] MSP430: Add defaulting to the insn length attribute Jozef Lawrynowicz
2020-07-23 15:56 ` [PATCH 4/5] MSP430: Implement TARGET_INSN_COST Jozef Lawrynowicz
2020-07-23 18:34 ` Segher Boessenkool
2020-07-24 11:50 ` Jozef Lawrynowicz
2020-07-24 12:25 ` Segher Boessenkool
2020-07-23 15:57 ` [PATCH 5/5] MSP430: Skip index-1.c test Jozef Lawrynowicz
2020-08-07 11:02 ` ping [PATCH 0/5] MSP430: Implement macros to describe relative costs of operations Jozef Lawrynowicz
2020-09-15 20:30 ` ping x2 " Jozef Lawrynowicz
2020-10-14 15:31 ` ping x3 " Jozef Lawrynowicz
2020-11-06 20:51 ` ping x4 " Jozef Lawrynowicz
2020-11-06 20:53 ` Jeff Law [this message]
2020-11-06 21:23 ` ping x2 " Jozef Lawrynowicz
2020-11-06 21:29 ` 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=9ae3290e-c76f-f756-fba6-74c59952da14@redhat.com \
--to=law@redhat.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).