From: Christophe Lyon <christophe.lyon@linaro.org>
To: Robert Suchanek <Robert.Suchanek@imgtec.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
"ebotcazou@adacore.com" <ebotcazou@adacore.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC][PATCH] Preferred rename register in regrename pass
Date: Tue, 10 Nov 2015 11:21:00 -0000 [thread overview]
Message-ID: <CAKdteObiHcfF3ZUzYdAdRMvqGywbQ8kTg5ZGZ06vKSTFNk5pRg@mail.gmail.com> (raw)
In-Reply-To: <B5E67142681B53468FAF6B7C31356562442C19BE@hhmail02.hh.imgtec.org>
On 9 November 2015 at 18:01, Robert Suchanek <Robert.Suchanek@imgtec.com> wrote:
> Hi,
>
>> On 11/09/2015 02:32 PM, Robert Suchanek wrote:
>> > The results below were generated for CSiBE benchmark and the numbers in
>> > columns express bytes in format 'net (gain/loss)' to show the difference
>> > with and without the patch when -frename-registers switch is used.
>>
>> I'm not entirely sure what the numbers represent. I can see how you'd
>> measure at a net size change (I assume a negative net is the intended
>> goal), but how did you arrive at gain/loss numbers?
>>
>> In any case, assuming negative is good, the results seem pretty decent.
>
> The gain/loss was calculated based on per function analysis.
> Each flavour e.g. MIPS n64 -Os was ran with/without the patch and compared to
> the base i.e. without the patch. The patched version of each function may
> show either positive (larger code size), negative or no difference to
> the code size. The gain/loss in a cell is the sum of all positive/negative
> numbers for a test. The negatives, as you said, are the good ones.
>
>>
>> > + gcc_assert
>> > + (terminated_this_insn->regno == REGNO (recog_data.operand[1]));
>>
>> Maybe break the line before the == so that you can start the arguments
>> on the same line as the assert.
>>
>> > + /* Nonzero if the chain is renamed. */
>> > + unsigned int renamed:1;
>>
>> I'd write "has already been renamed" since that is maybe slightly less
>> ambiguous.
>>
>> Ok with those changes.
>>
>>
>> Bernd
>
> Will do the changes and apply.
>
Hi,
Since you committed this (r230087 if I'm correct), I can see that GCC
fails to build
ligfortran for target arm-none-linuxgnueabi --with-cpu=cortex-a9.
The backtrace is:
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/libgfortran/generated/matmul_i8.c:
In function
'matmul_i8':
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/libgfortran/generated/matmul_i8.c:374:1:
internal compiler error: in scan_rtx_reg, at regrename.c:1074
}
^
0xa13940 scan_rtx_reg
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:1074
0xa1451d record_out_operands
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:1554
0xa14d12 build_def_use
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:1802
0xa1533e regrename_analyze(bitmap_head*)
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:726
0xa161f9 regrename_optimize
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:1871
0xa161f9 execute
/tmp/8079076_3.tmpdir/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/regrename.c:1908
Please submit a full bug report,
Can you have a look?
> Regards,
> Robert
>
next prev parent reply other threads:[~2015-11-10 11:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 14:40 Robert Suchanek
2015-09-17 17:11 ` Jeff Law
2015-09-17 21:28 ` Eric Botcazou
2015-09-18 15:29 ` Bernd Schmidt
2015-10-09 7:10 ` Robert Suchanek
2015-10-09 11:06 ` Bernd Schmidt
2015-10-09 11:20 ` Robert Suchanek
2015-11-09 13:32 ` Robert Suchanek
2015-11-09 16:30 ` Bernd Schmidt
2015-11-09 17:01 ` Robert Suchanek
2015-11-10 11:21 ` Christophe Lyon [this message]
2015-11-10 11:41 ` Robert Suchanek
2015-11-10 16:22 ` Christophe Lyon
2015-11-10 17:43 ` James Greenhalgh
2015-11-10 22:33 ` Robert Suchanek
2015-11-10 22:57 ` Bernd Schmidt
2015-11-11 0:06 ` Robert Suchanek
2015-11-11 8:50 ` Robert Suchanek
2015-11-12 7:47 ` Christophe Lyon
2015-11-12 12:57 ` Robert Suchanek
2015-11-10 12:10 ` Bernd Schmidt
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=CAKdteObiHcfF3ZUzYdAdRMvqGywbQ8kTg5ZGZ06vKSTFNk5pRg@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=Robert.Suchanek@imgtec.com \
--cc=bschmidt@redhat.com \
--cc=ebotcazou@adacore.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).