From: Richard Guenther <richard.guenther@gmail.com>
To: Tom de Vries <vries@codesourcery.com>
Cc: Richard Earnshaw <rearnsha@arm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, PR43920, 1/9] ARM specific part.
Date: Sat, 02 Apr 2011 07:47:00 -0000 [thread overview]
Message-ID: <BANLkTinVZAjcwHeaEn+g9X2GuMTWhrMWzA@mail.gmail.com> (raw)
In-Reply-To: <4D95F802.80003@codesourcery.com>
On Fri, Apr 1, 2011 at 6:06 PM, Tom de Vries <vries@codesourcery.com> wrote:
> On 04/01/2011 05:18 PM, Richard Earnshaw wrote:
>>
>> On Fri, 2011-04-01 at 16:45 +0200, Tom de Vries wrote:
>>> Reposting, with ChangeLog.
>>
>> #define BRANCH_COST(speed_p, predictable_p) \
>> - (TARGET_32BIT ? 4 : (optimize > 0 ? 2 : 0))
>> + (TARGET_32BIT ? (TARGET_THUMB2 && optimize_size ? 1 : 4) \
>> + : (optimize > 0 ? 2 : 0))
>>
>> Don't use optimize_size here, use !speed_p.
>>
>> Otherwise OK.
>>
>
> Replaced optimize_size by !speed_p.
I wonder if we can add a code-size test harness. Using GNU size
for examle, if available and a new dg-final { object-size SIZE } that
fails when the size is greater than the specified one (of course all
object-size tests with specific target restrictions).
I would have started on this myself, but my TCL-fu causes me to jump
off such tasks very quickly ;)
Richard.
> Thanks,
> - Tom
>
next prev parent reply other threads:[~2011-04-02 7:47 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 18:27 [PATCH, PR43920] Improve code-size optimizations Tom de Vries
2011-03-31 18:29 ` [PATCH, PR43920, 1/9] ARM specific part Tom de Vries
2011-04-01 14:46 ` Tom de Vries
2011-04-01 15:19 ` Richard Earnshaw
2011-04-01 16:06 ` Tom de Vries
2011-04-02 7:47 ` Richard Guenther [this message]
2011-04-02 17:06 ` Tom de Vries
2011-04-03 7:38 ` Richard Guenther
2011-04-03 17:03 ` Tom de Vries
[not found] ` <BANLkTikEruAfGJ392FXtasLv6-yV2tYSRQ@mail.gmail.com>
2011-04-04 12:14 ` Richard Guenther
2011-04-04 12:23 ` Rainer Orth
2011-04-05 13:35 ` Tom de Vries
2011-05-03 18:19 ` Rainer Orth
2011-04-03 18:40 ` Mike Stump
2011-03-31 18:31 ` [PATCH, PR43920, 2/9] ARM specific part - test case Tom de Vries
2011-04-01 14:47 ` Tom de Vries
2011-04-01 15:17 ` Tom de Vries
2011-04-01 15:34 ` Richard Earnshaw
2011-04-01 16:10 ` Tom de Vries
2011-04-05 10:43 ` Tom de Vries
2011-04-05 12:20 ` Richard Earnshaw
2011-04-06 10:48 ` Ramana Radhakrishnan
2011-04-06 12:29 ` Tom de Vries
2011-03-31 18:35 ` [PATCH, PR43920, 3/9] Cleanup Tom de Vries
2011-03-31 18:43 ` Jeff Law
2011-04-01 14:48 ` Tom de Vries
2011-04-01 15:15 ` Tom de Vries
2011-04-04 18:26 ` Jeff Law
2011-03-31 18:35 ` [PATCH, PR43920, 4-9/9] Cross-jumping Tom de Vries
2011-03-31 18:36 ` [PATCH, PR43920, 4/9] Cross-jumping - Don't count use or clobber Tom de Vries
2011-03-31 18:40 ` Jeff Law
2011-03-31 19:09 ` Tom de Vries
2011-03-31 19:19 ` Jeff Law
2011-04-01 14:48 ` Tom de Vries
2011-04-04 19:11 ` Jeff Law
2011-03-31 18:42 ` [PATCH, PR43920, 5/9] Cross-jumping - Add missing use of return register Tom de Vries
2011-03-31 18:52 ` Jeff Law
2011-04-01 14:49 ` Tom de Vries
2011-04-04 19:11 ` Jeff Law
2011-03-31 18:44 ` [PATCH, PR43920, 6/9] Cross-jumping - Use reg-notes Tom de Vries
2011-03-31 18:56 ` Jeff Law
2011-03-31 21:25 ` Tom de Vries
2011-04-01 14:54 ` Tom de Vries
2011-04-04 16:14 ` Tom de Vries
2011-04-06 17:41 ` Jeff Law
2011-03-31 18:45 ` [PATCH, PR43920, 7/9] Cross-jumping - Extend search scope Tom de Vries
2011-03-31 18:58 ` Jeff Law
2011-04-05 11:44 ` Tom de Vries
2011-04-01 14:55 ` Tom de Vries
2011-04-05 21:45 ` Jeff Law
2011-03-31 18:46 ` [PATCH, PR43920, 8/9] Cross-jumping - Extend search scope - test case Tom de Vries
2011-03-31 19:00 ` Jeff Law
2011-04-01 14:56 ` Tom de Vries
2011-04-01 15:01 ` Jakub Jelinek
2011-04-01 15:18 ` Tom de Vries
2011-04-01 16:14 ` Tom de Vries
2011-04-05 21:46 ` Jeff Law
2011-03-31 18:56 ` [PATCH, PR43920, 9/9] Cross-jumping - Allow both directions Tom de Vries
2011-03-31 19:02 ` Jeff Law
2011-04-01 14:56 ` Tom de Vries
2011-04-05 21:46 ` Jeff Law
2011-03-31 21:16 ` [PATCH, PR43920] Improve code-size optimizations Eric Botcazou
2011-04-01 15:06 ` Tom de Vries
2011-04-01 16:06 ` Eric Botcazou
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=BANLkTinVZAjcwHeaEn+g9X2GuMTWhrMWzA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rearnsha@arm.com \
--cc=vries@codesourcery.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).