public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/55430] [4.8 Regression] LRA miscompilation of ree.c Date: Fri, 23 Nov 2012 01:29:00 -0000 [thread overview] Message-ID: <bug-55430-4-J35Z6udTG9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55430-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55430 --- Comment #2 from Vladimir Makarov <vmakarov at gcc dot gnu.org> 2012-11-23 01:29:13 UTC --- Author: vmakarov Date: Fri Nov 23 01:29:07 2012 New Revision: 193742 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193742 Log: 2012-11-22 Vladimir Makarov <vmakarov@redhat.com> PR middle-end/55430 * lra.c: Move #include "hard-reg-set.h" before #include "rtl.h". (new_insn_reg): Update biggest_mode. (collect_non_operand_hard_regs): Check eliminable regs too. (initialize_lra_reg_info_element): Initialize biggest_mode. (add_regs_to_insn_regno_info): Ignore non-allocatable non-eliminable hard regs. (lra.c): Move setting lra_no_alloc_regs before init_insn_recog_data. * lra-constraints.c (simplify_operand_subreg): Add a comment. (lra_constraints): Ignore equivalent memory of regs occuring in paradoxical subregs. * lra-lives.c (lra_create_live_ranges): Add a comment. Modified: trunk/gcc/ChangeLog trunk/gcc/lra-constraints.c trunk/gcc/lra-lives.c trunk/gcc/lra.c
next prev parent reply other threads:[~2012-11-23 1:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-21 17:07 [Bug other/55430] New: [4.8 Regression jakub at gcc dot gnu.org 2012-11-21 17:16 ` [Bug middle-end/55430] " jakub at gcc dot gnu.org 2012-11-23 1:29 ` vmakarov at gcc dot gnu.org [this message] 2012-11-23 15:14 ` [Bug middle-end/55430] [4.8 Regression] LRA miscompilation of ree.c jakub at gcc dot gnu.org 2012-11-27 11:07 ` 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-55430-4-J35Z6udTG9@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).