public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/48253] [4.6/4.7 Regression] Further .debug_aranges issues Date: Tue, 29 Mar 2011 02:31:00 -0000 [thread overview] Message-ID: <bug-48253-4-zIJju8pL1p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48253-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48253 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-28 23:55:49 UTC --- Author: jakub Date: Mon Mar 28 23:55:47 2011 New Revision: 171642 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=171642 Log: PR debug/48253 * dwarf2out.c (struct dw_fde_struct): Remove dw_fde_hot_section_label, dw_fde_hot_section_end_label, dw_fde_unlikely_section_label, dw_fde_unlikely_section_end_label, cold_in_std_section, dw_fde_switched_sections and dw_fde_switched_cold_to_hot fields. Add dw_fde_second_begin, dw_fde_second_end and second_in_std_section fields. (output_fde): Use dw_fde_second_{begin,end} if second is true, otherwise dw_fde_{begin,end}. (output_call_frame_info): Test dw_fde_second_begin != NULL instead of dw_fde_switched_sections. (dwarf2out_begin_prologue): Stop initializing removed dw_fde_struct fields, initialize new fields. Initialize in_std_section unconditionally from the first partition. (dwarf2out_end_epilogue): Don't override dw_fde_end when dw_fde_second_begin is non-NULL. (dwarf2out_switch_text_section): Stop initializing removed dw_fde_struct fields, initialize new fields, initialize also dw_fde_end here. Set dw_fde_switch_cfi even when dwarf2out_do_cfi_asm (). Call var_location_switch_text_section. (struct var_loc_list_def): Add last_before_switch field. (arange_table, arange_table_allocated, arange_table_in_use, ARANGE_TABLE_INCREMENT, add_arange): Removed. (size_of_aranges): Count !in_std_section and !second_in_std_section hunks in fdes, instead of looking at arange_table_in_use. (output_aranges): Add aranges_length argument, don't call size_of_aranges here. Instead of using aranges_table* emit ranges for fdes when !in_std_section resp. !second_in_std_section. (dw_loc_list): Break ranges crossing section switch. (convert_cfa_to_fb_loc_list): Likewise. If switched sections, use dw_fde_second_end instead of dw_fde_end as end of last range. (gen_subprogram_die): Don't call add_arange. Use dw_fde_{begin,end} for first partition and if switched section dw_fde_second_{begin,end} for the second. (var_location_switch_text_section_1, var_location_switch_text_section): New functions. (dwarf2out_begin_function): Initialize cold_text_section even when function_section () isn't text_section. (prune_unused_types): Don't walk arange_table. (dwarf2out_finish): Don't needlessly test flag_reorder_blocks_and_partition when testing cold_text_section_used. If info_section_emitted, call size_of_aranges and if it indicates non-empty .debug_aranges, call output_aranges with the computed size. Stop using removed dw_fde_struct fields, use dw_fde_{begin,end} for first partition and dw_fde_second_{begin,end} for second. Modified: trunk/gcc/ChangeLog trunk/gcc/dwarf2out.c
next prev parent reply other threads:[~2011-03-28 23:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-23 13:08 [Bug debug/48253] New: " jakub at gcc dot gnu.org 2011-03-23 13:11 ` [Bug debug/48253] " jakub at gcc dot gnu.org 2011-03-23 14:49 ` jakub at gcc dot gnu.org 2011-03-24 16:34 ` rguenth at gcc dot gnu.org 2011-03-29 2:31 ` jakub at gcc dot gnu.org [this message] 2011-03-29 20:30 ` [Bug debug/48253] [4.6 " jakub at gcc dot gnu.org 2011-03-29 22:56 ` jakub at gcc dot gnu.org 2011-03-30 0:07 ` jakub at gcc dot gnu.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=bug-48253-4-zIJju8pL1p@http.gcc.gnu.org/bugzilla/ \ --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).