public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/24444] [4.1 regression] invalid register in debug info Date: Mon, 31 Oct 2005 23:39:00 -0000 [thread overview] Message-ID: <20051031233935.6379.qmail@sourceware.org> (raw) In-Reply-To: <bug-24444-50@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from wilson at gcc dot gnu dot org 2005-10-31 23:39 ------- Subject: Bug 24444 Author: wilson Date: Mon Oct 31 23:39:29 2005 New Revision: 106299 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106299 Log: Restore old AT_frame_base code for targets that don't use dwarf2 unwind info. Partial fix. PR debug/24444 * dwarf2out.c (convert_cfa_to_loc_list): Put inside DWARF2_UNWIND_INFO ifdef. Put ifdefs around call in gen_subprogram_die. (compute_frame_pointer_to_cfa_displacement): Likewise. (gen_subprogram_die): Restore old code for when DWARF2_UNWIND_INFO is not defined. Modified: trunk/gcc/ChangeLog trunk/gcc/dwarf2out.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24444
next prev parent reply other threads:[~2005-10-31 23:39 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-19 17:02 [Bug debug/24444] New: " schwab at suse dot de 2005-10-19 17:03 ` [Bug debug/24444] " schwab at suse dot de 2005-10-19 23:34 ` wilson at gcc dot gnu dot org 2005-10-20 5:09 ` wilson at gcc dot gnu dot org 2005-10-20 8:36 ` rth at gcc dot gnu dot org 2005-10-21 0:53 ` wilson at gcc dot gnu dot org 2005-10-31 6:32 ` mmitchel at gcc dot gnu dot org 2005-10-31 23:39 ` wilson at gcc dot gnu dot org [this message] 2005-10-31 23:46 ` wilson at gcc dot gnu dot org 2005-11-01 1:16 ` wilson at gcc dot gnu dot org 2005-11-15 20:58 ` drow at false dot org 2006-02-03 8:40 ` [Bug debug/24444] [4.1/4.2 " aoliva at gcc dot gnu dot org 2006-02-03 18:49 ` pinskia at gcc dot gnu dot org 2006-02-04 22:08 ` aoliva at gcc dot gnu dot org 2006-02-04 22:13 ` aoliva at gcc dot gnu dot org 2006-02-04 22:23 ` pinskia at gcc dot gnu dot org 2006-02-07 6:51 ` jakub at gcc dot gnu dot org 2006-02-07 6:52 ` jakub at gcc dot gnu dot org 2006-02-21 0:33 ` patchapp at dberlin 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=20051031233935.6379.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).