public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ddaney at avtrex dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/29132] [4.1/4.2 Regression] Mips exception handling broken.
Date: Mon, 18 Sep 2006 21:33:00 -0000	[thread overview]
Message-ID: <20060918213254.23127.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29132-7151@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from ddaney at avtrex dot com  2006-09-18 21:32 -------
Subject: Re:  [4.2 Regression] Mips exception handling broken.

roger at eyesopen dot com wrote:
> ------- Comment #1 from roger at eyesopen dot com  2006-09-18 21:27 -------
> Hi David,
> 
> I was wondering if you have a MIPS tree handy, whether you could easily
> test the following single line patch:
> 
> Index: dwarf2out.c
> ===================================================================
> *** dwarf2out.c (revision 117035)
> --- dwarf2out.c (working copy)
> *************** dwarf2out_begin_prologue (unsigned int l
> *** 2572,2578 ****
>     fde = &fde_table[fde_table_in_use++];
>     fde->decl = current_function_decl;
>     fde->dw_fde_begin = dup_label;
> !   fde->dw_fde_current_label = NULL;
>     fde->dw_fde_hot_section_label = NULL;
>     fde->dw_fde_hot_section_end_label = NULL;
>     fde->dw_fde_unlikely_section_label = NULL;
> --- 2572,2578 ----
>     fde = &fde_table[fde_table_in_use++];
>     fde->decl = current_function_decl;
>     fde->dw_fde_begin = dup_label;
> !   fde->dw_fde_current_label = dup_label;
>     fde->dw_fde_hot_section_label = NULL;
>     fde->dw_fde_hot_section_end_label = NULL;
>     fde->dw_fde_unlikely_section_label = NULL;
> 
> Due to all the abstraction with debugging formats, its difficult to tell the
> order in which things get executed, and whether this initial value for
> dw_fde_current_label survives long enough to avoid use of a set_loc.
> 

I will try the patch now.  A full build with libgcj will take me several 
hours to build and test.

David Daney.


-- 


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


  parent reply	other threads:[~2006-09-18 21:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 20:46 [Bug c/29132] New: [4.2 " daney at gcc dot gnu dot org
2006-09-18 21:28 ` [Bug c/29132] " roger at eyesopen dot com
2006-09-18 21:32 ` [Bug debug/29132] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-09-18 21:33 ` ddaney at avtrex dot com [this message]
2006-09-18 21:59 ` ddaney at avtrex dot com
2006-09-19  5:58 ` daney at gcc dot gnu dot org
2006-09-21  2:34 ` mmitchel at gcc dot gnu dot org
2006-09-21 17:13 ` sayle at gcc dot gnu dot org
2006-09-22 16:51 ` [Bug debug/29132] [4.1 " roger at eyesopen dot com
2006-09-24 15:56 ` sayle at gcc dot gnu dot org
2006-09-25  3:23 ` pinskia 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=20060918213254.23127.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: 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).