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/55686] [4.8 Regression] ICE in assign_by_spills, at lra-assigns.c:1244 Date: Tue, 22 Jan 2013 09:20:00 -0000 [thread overview] Message-ID: <bug-55686-4-9IUqc0lXSk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55686-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55686 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-22 09:19:18 UTC --- Created attachment 29245 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29245 gcc48-pr55686.patch The UNSPEC_STOS way, untested so far. This doesn't attempt to solve the other issue, but I believe it isn't a regression, thus perhaps we could postpone the rest for 4.9?
next prev parent reply other threads:[~2013-01-22 9:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-14 9:25 [Bug rtl-optimization/55686] New: " rguenth at gcc dot gnu.org 2012-12-14 9:25 ` [Bug rtl-optimization/55686] " rguenth at gcc dot gnu.org 2012-12-14 10:03 ` rguenth at gcc dot gnu.org 2012-12-14 11:16 ` mpolacek at gcc dot gnu.org 2012-12-14 11:26 ` jakub at gcc dot gnu.org 2012-12-14 11:27 ` jakub at gcc dot gnu.org 2012-12-14 15:13 ` vmakarov at gcc dot gnu.org 2012-12-14 16:34 ` jakub at gcc dot gnu.org 2012-12-17 15:41 ` steven at gcc dot gnu.org 2012-12-19 15:29 ` rguenth at gcc dot gnu.org 2012-12-19 15:32 ` jakub at gcc dot gnu.org 2012-12-21 13:48 ` hubicka at ucw dot cz 2013-01-07 15:31 ` rguenth at gcc dot gnu.org 2013-01-22 9:20 ` jakub at gcc dot gnu.org [this message] 2013-01-22 16:42 ` jakub at gcc dot gnu.org 2013-01-22 17:05 ` 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-55686-4-9IUqc0lXSk@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).