public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manjian2006 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/60438] [4.9 Regression] dwarf2cfi :2239 still assert,not the same cause as PR 59575
Date: Mon, 10 Mar 2014 13:03:00 -0000	[thread overview]
Message-ID: <bug-60438-4-VHxfvOuF1D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60438-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60438

--- Comment #28 from linzj <manjian2006 at gmail dot com> ---
(In reply to Jakub Jelinek from comment #27)
> Wonder if we just shouldn't pass the other insn (the one we'd like to
> delete) to
> try_apply_stack_adjustment and if either of them is frame related insn,
> check harder to see if we can handle it or give up if we can't handle it.
> At least merging of a frame related stack adjustment and following non-frame
> related one (or vice versa?) is I think very common.

I think the final solution will both a fulfillment of dwarf2cfi & csa & jump2.
That is csa is able to combine the stack operations,jump2 is able to find the
common insn in ends of blocks,and dwarf2cfi is able to get the correct input
data.


  parent reply	other threads:[~2014-03-10 13:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  6:54 [Bug debug/60438] New: " manjian2006 at gmail dot com
2014-03-06  6:56 ` [Bug debug/60438] " manjian2006 at gmail dot com
2014-03-06  6:59 ` manjian2006 at gmail dot com
2014-03-06  7:37 ` manjian2006 at gmail dot com
2014-03-07  8:53 ` manjian2006 at gmail dot com
2014-03-07  8:59 ` manjian2006 at gmail dot com
2014-03-07  9:24 ` manjian2006 at gmail dot com
2014-03-07  9:48 ` manjian2006 at gmail dot com
2014-03-07 10:09 ` manjian2006 at gmail dot com
2014-03-07 14:28 ` manjian2006 at gmail dot com
2014-03-07 18:08 ` manjian2006 at gmail dot com
2014-03-07 22:05 ` jakub at gcc dot gnu.org
2014-03-07 22:07 ` [Bug debug/60438] [4.9 Regression] " jakub at gcc dot gnu.org
2014-03-08  2:59 ` manjian2006 at gmail dot com
2014-03-08  6:33 ` manjian2006 at gmail dot com
2014-03-08  6:42 ` manjian2006 at gmail dot com
2014-03-08 10:04 ` manjian2006 at gmail dot com
2014-03-08 10:43 ` manjian2006 at gmail dot com
2014-03-09  0:03 ` rth at gcc dot gnu.org
2014-03-09  2:23 ` manjian2006 at gmail dot com
2014-03-09  4:10 ` rth at gcc dot gnu.org
2014-03-09  5:37 ` manjian2006 at gmail dot com
2014-03-09 10:23 ` manjian2006 at gmail dot com
2014-03-09 10:25 ` manjian2006 at gmail dot com
2014-03-09 10:29 ` manjian2006 at gmail dot com
2014-03-09 15:02 ` manjian2006 at gmail dot com
2014-03-10 10:18 ` jakub at gcc dot gnu.org
2014-03-10 11:04 ` manjian2006 at gmail dot com
2014-03-10 11:32 ` jakub at gcc dot gnu.org
2014-03-10 13:03 ` manjian2006 at gmail dot com [this message]
2014-03-10 19:23 ` rth at gcc dot gnu.org
2014-03-10 19:26 ` jakub at gcc dot gnu.org
2014-03-10 20:51 ` rth at gcc dot gnu.org
2014-03-11 15:12 ` jakub at gcc dot gnu.org
2014-03-12 17:25 ` rth at gcc dot gnu.org
2014-03-12 17:29 ` jakub at gcc dot gnu.org
2014-03-13  9:00 ` jakub at gcc dot gnu.org
2014-03-13 20:25 ` rth at gcc dot gnu.org
2014-03-13 20:56 ` jakub at gcc dot gnu.org
2014-03-18 13:08 ` bernd.edlinger at hotmail dot de
2014-03-18 13:16 ` dominiq at lps dot ens.fr
2014-03-18 15:10 ` manjian2006 at gmail dot com

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-60438-4-VHxfvOuF1D@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: 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).