From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [0/3] Fix PR78120, in ifcvt/rtlanal/i386.
Date: Thu, 24 Nov 2016 22:32:00 -0000 [thread overview]
Message-ID: <20161124223241.GA30675@gate.crashing.org> (raw)
In-Reply-To: <20161124161423.GG14394@gate.crashing.org>
On Thu, Nov 24, 2016 at 10:14:24AM -0600, Segher Boessenkool wrote:
> On Thu, Nov 24, 2016 at 08:48:04AM -0700, Jeff Law wrote:
> > On 11/24/2016 07:53 AM, Segher Boessenkool wrote:
> > >
> > >That we compare different kinds of costs (which really has no meaning at
> > >all, it's a heuristic at best) in various places is a known problem, not
> > >a regression.
> > But the problems with the costing system exhibit themselves as a code
> > quality regression. In the end that's what the end-users see -- a
> > regression in the quality of the code GCC generates.
>
> Yes, exactly -- and I fear this all-encompassing change will cause just
> such a regression for many users. Tests are running, will know more
> later today (or tomorrow).
>
> The PR is about a very specific problem; the patch is not. The patch
> is not a bug fix. If we allow anything that "makes things better" in
> stage 3, what make it different from stage 1 then?
Here are results of testing with trunk right before the three patches,
compared with with the three patches. This lists the sizes of the vmlinux
of a Linux kernel build for that arch.
better:
blackfin 1973931 1973867
frv 3638192 3637792
h8300 1060172 1059976
i386 9742984 9742463
ia64 15402035 15396171
mips 4286748 4286692
mn10300 2360025 2358201
nios2 3185625 3176693
x86_64 10360418 10359588
worse:
alpha 5439003 5455979
c6x 2107939 2108931
cris 2189380 2193836
m32r 3427409 3427453
m68k 3228408 3230978
mips64 5564819 5565291
parisc 8278881 8289573
parisc64 7234619 7249139
powerpc 8438949 8440005
powerpc64 14499969 14508689
s390 12778748 12779220
shnommu 1369868 1371020
sparc64 5921556 5922172
tilegx 12297581 12307461
tilepro 11215603 11227339
xtensa 1776196 1779152
does not build:
arc 0 0
arm 0 0
arm64 0 0
microblaze 0 0
sh 0 0
sparc 0 0
Segher
next prev parent reply other threads:[~2016-11-24 22:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 18:58 [0/3] Fix PR71280, " Bernd Schmidt
2016-11-23 19:00 ` [0/3] Fix PR78120, " Bernd Schmidt
2016-11-23 19:30 ` Jeff Law
2016-11-23 19:31 ` Bernd Schmidt
2016-11-24 14:21 ` Segher Boessenkool
2016-11-24 14:26 ` Bernd Schmidt
2016-11-24 14:36 ` Segher Boessenkool
2016-11-24 14:38 ` Bernd Schmidt
2016-11-24 14:44 ` Eric Botcazou
2016-11-24 14:54 ` Segher Boessenkool
2016-11-24 15:16 ` Richard Biener
2016-11-24 15:46 ` Jeff Law
2016-11-24 15:34 ` Bernd Schmidt
2016-11-24 15:48 ` Jeff Law
2016-11-24 16:14 ` Segher Boessenkool
2016-11-24 22:32 ` Segher Boessenkool [this message]
2016-11-26 10:44 ` Jeff Law
2016-11-26 11:11 ` Eric Botcazou
2016-11-26 16:15 ` Jeff Law
2016-11-26 22:03 ` Segher Boessenkool
2016-11-26 18:08 ` Segher Boessenkool
2016-11-25 9:15 ` Richard Biener
2016-11-25 15:34 ` Jeff Law
2016-11-25 15:55 ` Segher Boessenkool
2016-11-28 8:59 ` Bernd Schmidt
2016-11-28 9:05 ` Bernd Schmidt
2016-11-28 18:50 ` Jeff Law
2016-11-28 18:52 ` Bernd Schmidt
2016-11-23 19:01 ` Bernd Schmidt
2016-11-23 21:46 ` Uros Bizjak
2016-11-23 19:03 ` [3/3] " Bernd Schmidt
2016-11-23 19:38 ` 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=20161124223241.GA30675@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).