public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/24444] [4.1/4.2 regression] invalid register in debug info
Date: Sat, 04 Feb 2006 22:08:00 -0000 [thread overview]
Message-ID: <20060204220809.24432.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24444-50@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from aoliva at gcc dot gnu dot org 2006-02-04 22:08 -------
Subject: Bug 24444
Author: aoliva
Date: Sat Feb 4 22:08:04 2006
New Revision: 110594
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110594
Log:
PR debug/24444
* config/ia64/ia64.c: Include debug.h.
(MAX_ARTIFICIAL_LABEL_BYTES): New.
(ia64_label_after_insn, ia64_dwarf2out_def_steady_cfa): New.
(IA64_CHANGE_CFA_IN_EPILOGUE): Define to 0.
(process_epilogue, process_set, process_for_unwind_directive):
Output unwind info only if requested. Add CFA info if requested.
Add new arguments as needed. Adjust callers.
* config/ia64/ia64.h (ARG_POINTER_CFA_OFFSET): Override
incorrect default.
(DWARF2_FRAME_INFO): Define to zero.
* config/ia64/unwind-ia64.c: Remove code that compensated for
the CFA offset error fixed above.
* config/ia64/t-ia64 (ia64.o): Depend on debug.h.
* dwarf2out.c (DWARF2_FRAME_INFO): Define default.
(dwarf2out_do_frame): Require nonzero DWARF2_UNWIND_INFO for
-funwind-tables and -fexceptions to enable frame info.
(dwarf2out_frame_init): Define initial CFA even if
DWARF2_UNWIND_INFO is disabled. Call initial_return_save if
DWARF2_UNWIND_INFO is nonzero, not just defined.
(dwarf2out_frame_finish): Output non-EH call frame info only
if DWARF2_FRAME_INFO is nonzero.
(convert_cfa_to_loc_list,
compute_frame_pointer_to_cfa_displacement): Define even if
unwind info is not supported.
(gen_subprogram_die): Use the above unconditionally. Remove
legacy alternate code.
* toplev.c (compile_file): Compile in call to
dwarf2out_frame_finish if DWARF2_DEBUGGING_INFO is defined.
(lang_dependent_init): Ditto for dwarf2out_frame_init.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/ia64/ia64.c
trunk/gcc/config/ia64/ia64.h
trunk/gcc/config/ia64/t-ia64
trunk/gcc/config/ia64/unwind-ia64.c
trunk/gcc/dwarf2out.c
trunk/gcc/toplev.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24444
next prev parent reply other threads:[~2006-02-04 22:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:02 [Bug debug/24444] New: [4.1 " 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
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 [this message]
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=20060204220809.24432.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).