[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-11-15 Thread drow at false dot org
--- Comment #9 from drow at gcc dot gnu dot org 2005-11-15 20:58 --- Subject: Re: [4.1 regression] invalid register in debug info On Thu, Oct 20, 2005 at 08:35:59AM -, rth at gcc dot gnu dot org wrote: Well, the ideal fix is to make use of the dwarf3 DW_OP_call_frame_cfa

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-31 Thread wilson at gcc dot gnu dot org
--- Comment #6 from wilson at gcc dot gnu dot org 2005-10-31 23:39 --- Subject: Bug 2 Author: wilson Date: Mon Oct 31 23:39:29 2005 New Revision: 106299 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=106299 Log: Restore old AT_frame_base code for targets that don't use dwarf2

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-31 Thread wilson at gcc dot gnu dot org
--- Comment #7 from wilson at gcc dot gnu dot org 2005-10-31 23:46 --- This is partially fixed. The debug info is correct enough to make the gdb testsuite happy, but we are lacking correct info for the frame_base in the prologue and epilogue. That used to be computed by code in

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-31 Thread wilson at gcc dot gnu dot org
--- Comment #8 from wilson at gcc dot gnu dot org 2005-11-01 01:16 --- I see that we are using the priority field now, so let's put the 4.1 target milestone back and set priority to p4 to indicate this is a regression, but not a serious one blocking the release. -- wilson at gcc dot

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-30 Thread mmitchel at gcc dot gnu dot org
--- Comment #5 from mmitchel at gcc dot gnu dot org 2005-10-31 06:32 --- I guess I'll leave this as P2, but I really do think we should find a fix before the next release, for the affected targets. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-20 Thread rth at gcc dot gnu dot org
--- Comment #4 from rth at gcc dot gnu dot org 2005-10-20 08:35 --- Well, the ideal fix is to make use of the dwarf3 DW_OP_call_frame_cfa directive, and let the debugger get the CFA information from the ia64 unwind info. Similarly for the arm eabi unwind info. I'm not sure what a good

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-20 Thread wilson at gcc dot gnu dot org
-- wilson at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-19 Thread schwab at suse dot de
--- Comment #1 from schwab at suse dot de 2005-10-19 17:03 --- Created an attachment (id=10025) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10025action=view) Testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-19 Thread wilson at gcc dot gnu dot org
--- Comment #2 from wilson at gcc dot gnu dot org 2005-10-19 23:34 --- This was broken by Richard Henderson's patch that added the convert_cfa_to_loc_list function. The thread for the patch starts here. It was finally installed Sept 7.

[Bug debug/24444] [4.1 regression] invalid register in debug info

2005-10-19 Thread wilson at gcc dot gnu dot org
--- Comment #3 from wilson at gcc dot gnu dot org 2005-10-20 05:09 --- It looks a little more complicated than I hoped, as Richard deleted code in var-tracking.c that was used by the old code in dwarf2out.c that we need for IA-64 and other non-DWARF2_UNWIND_INFO targets. -- wilson