public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/42288] please emit empty .debug_aranges section Date: Mon, 26 Sep 2011 18:24:00 -0000 [thread overview] Message-ID: <bug-42288-4-7hDgyOIt0L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-42288-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42288 Mark Wielaard <mark at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Mark Wielaard <mark at gcc dot gnu.org> 2011-09-26 18:15:52 UTC --- Author: mark Date: Tue May 3 19:36:08 2011 New Revision: 173340 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173340 Log: PR42288 emit empty .debug_aranges section. * dwarf2out.c (dwarf2out_finish): Always call output_aranges () when info_section_emitted. Modified: trunk/gcc/ChangeLog trunk/gcc/dwarf2out.c
next prev parent reply other threads:[~2011-09-26 18:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-42288-4@http.gcc.gnu.org/bugzilla/> 2011-04-21 15:33 ` mark at gcc dot gnu.org 2011-09-26 18:24 ` mark at gcc dot gnu.org [this message] 2009-12-04 22:36 [Bug debug/42288] New: " tromey at gcc dot gnu dot org 2009-12-06 22:31 ` [Bug debug/42288] " rth at gcc dot gnu dot org 2009-12-07 2:05 ` rth at gcc dot gnu dot org 2009-12-07 15:57 ` tromey at gcc dot gnu dot org 2009-12-07 16:19 ` rth at gcc dot gnu dot org 2009-12-08 17:59 ` tromey at gcc dot gnu dot org 2009-12-15 17:36 ` rth 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=bug-42288-4-7hDgyOIt0L@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).