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 rtl-optimization/55396] -O2 -m32 -fno-omit-frame-pointer: internal compiler error: in check_rtl, at lra.c:2007 Date: Tue, 20 Nov 2012 21:33:00 -0000 [thread overview] Message-ID: <bug-55396-4-2a1zJZNXsm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55396-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55396 --- Comment #2 from Vladimir Makarov <vmakarov at gcc dot gnu.org> 2012-11-20 21:33:12 UTC --- Author: vmakarov Date: Tue Nov 20 21:32:59 2012 New Revision: 193678 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193678 Log: 2012-11-20 Vladimir Makarov <vmakarov@redhat.com> PR rtl-optimization/55396 * lra-constraints.c (get_reload_reg): Change class if it is different from reg class. Modified: trunk/gcc/ChangeLog trunk/gcc/lra-constraints.c
next prev parent reply other threads:[~2012-11-20 21:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-19 19:49 [Bug rtl-optimization/55396] New: " gcc at breakpoint dot cc 2012-11-20 8:44 ` [Bug rtl-optimization/55396] " markus at trippelsdorf dot de 2012-11-20 21:33 ` vmakarov at gcc dot gnu.org [this message] 2012-11-21 20:25 ` gcc at breakpoint dot cc
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-55396-4-2a1zJZNXsm@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).