This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/44664] CU DW_AT_low_pc, DW_AT_entry_pc are 0x0
- From: "mark at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 01 May 2012 15:00:01 +0000
- Subject: [Bug debug/44664] CU DW_AT_low_pc, DW_AT_entry_pc are 0x0
- Auto-submitted: auto-generated
- References: <bug-44664-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44664
Mark Wielaard <mark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-05-01
CC| |mark at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #2 from Mark Wielaard <mark at gcc dot gnu.org> 2012-05-01 15:00:01 UTC ---
I think the DW_AT_entry_pc issue was resolved by:
commit cb18bd3ce42532858cc65a1f20f3d79d5c253dde
Author: mark <mark@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Fri Apr 1 18:24:52 2011 +0000
Don't add DW_AT_low_pc if the CU has no associated code.
* dwarf2out.c (dwarf2out_finish): Don't add low_pc and/or
high_pc attribute if the CU has no associated code. Only output
DW_AT_entry_pc for CU if not generating strict dwarf and
dwarf_version < 4.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@171846
138bc75d-0d04-0410-96
Since comment #1 said "So, from (a) IMHO only the point about DW_AT_entry_pc
not allowed on CU is valid." Can this issue now be closed?