public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57189] [4.9 Regression] Vector register is spilled for vector extract pattern Date: Tue, 17 Dec 2013 11:12:00 -0000 [thread overview] Message-ID: <bug-57189-4-hn2ZM80Tkt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57189-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57189 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Uroš Bizjak from comment #4) > (In reply to Jakub Jelinek from comment #3) > > Likely caused by r198611. > > This is the patch that exposes the problem. > > I have filled this PR due to the difference with IRA vs. reload, it looks > that spill size should be somehow taken into account. What was the point of the r198611 patch other than macroizing some insns though? Isn't it worth to just restore the previous behavior when it worked properly with both reload and LRA? >From gcc-bugs-return-437825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 17 11:12:48 2013 Return-Path: <gcc-bugs-return-437825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18909 invoked by alias); 17 Dec 2013 11:12:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 18878 invoked by uid 48); 17 Dec 2013 11:12:44 -0000 From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/59535] [4.9 regression] -Os code size regressions for Thumb1/Thumb2 with LRA Date: Tue, 17 Dec 2013 11:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rearnsha at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: <bug-59535-4-E67rtcKSam@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59535-4@http.gcc.gnu.org/bugzilla/> References: <bug-59535-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg01480.txt.bz2 Content-length: 757 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY535 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.9 regression] -Os code |[4.9 regression] -Os code |size regressions for |size regressions for |Thumb1/Thumb2 (with LRA)? |Thumb1/Thumb2 with LRA --- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- It seems that one of the major problems is a significant increase in the number of mov instructions to copy registers from one location to another. This is probably due to the two-operand format instructions we have in Thumb.
next prev parent reply other threads:[~2013-12-17 11:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-06 17:46 [Bug rtl-optimization/57189] New: " ubizjak at gmail dot com 2013-05-07 8:51 ` [Bug rtl-optimization/57189] " rguenth at gcc dot gnu.org 2013-05-07 8:51 ` rguenth at gcc dot gnu.org 2013-10-25 13:13 ` graham.stott at btinternet dot com 2013-11-27 11:48 ` jakub at gcc dot gnu.org 2013-11-27 11:55 ` ubizjak at gmail dot com 2013-12-17 11:12 ` jakub at gcc dot gnu.org [this message] 2013-12-17 11:33 ` ubizjak at gmail dot com 2014-03-13 15:53 ` vmakarov at gcc dot gnu.org 2014-03-13 15:56 ` jakub at gcc dot gnu.org
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=bug-57189-4-hn2ZM80Tkt@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).