public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at bigpond dot net dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40473] -mno-sched-prolog breaks function parameter debug location lists Date: Wed, 17 Jun 2009 14:36:00 -0000 [thread overview] Message-ID: <20090617143613.32717.qmail@sourceware.org> (raw) In-Reply-To: <bug-40473-1057@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from amodra at bigpond dot net dot au 2009-06-17 14:36 ------- Created an attachment (id=18016) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18016&action=view) patch proposal Actually, it doesn't look all that hard to fix. The attached patch is a little horrible in that it doesn't use the normal method of insert_insn_on_edge(), commit_edge_insertions(), but we are too late for that. I tried, and found verify_flow_info() in commit_edge_insertions() was bombing on stuff already present. Patch currently bootstrapping with BOOT_CFLAGS="-g -O2 -mno-sched-prolog". -- amodra at bigpond dot net dot au changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |amodra at bigpond dot net |dot org |dot au Status|UNCONFIRMED |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40473
next prev parent reply other threads:[~2009-06-17 14:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-17 9:21 [Bug target/40473] New: " amodra at bigpond dot net dot au 2009-06-17 9:21 ` [Bug target/40473] " amodra at bigpond dot net dot au 2009-06-17 13:12 ` Andrew Thomas Pinski 2009-06-17 13:13 ` pinskia at gmail dot com 2009-06-17 14:36 ` amodra at bigpond dot net dot au [this message] 2009-09-23 0:23 ` amodra at gcc dot gnu dot org 2009-09-23 22:19 ` amodra at gcc dot gnu dot org 2009-09-23 22:30 ` amodra at gcc dot gnu dot org 2009-09-23 22:39 ` amodra at bigpond dot net dot au 2009-10-02 17:12 ` bergner at gcc dot gnu dot 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=20090617143613.32717.qmail@sourceware.org \ --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).