This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/19087] Overflowed address in dwarf debug line information
- From: "bjoern dot m dot haase at web dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 May 2005 21:40:08 -0000
- Subject: [Bug target/19087] Overflowed address in dwarf debug line information
- References: <20041220095410.19087.tsandnes@atmel.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bjoern dot m dot haase at web dot de 2005-05-30 21:40 -------
OK,
sorry for this, but I just realized that Darcy Watkins has made a couple of
almost exactly identical observations. Did not review all of the more recent
comments.
In case that the only remaining problem turns out to be the trailing 0x80 that
indicate the memory space, one way to handle it could be to change the way the
asm output is generated. I.e. there is a quite easy method for forcing gcc to
generate
.long ((lable_referenced_within_the_dwarf_section) & 0x0001FFFF)
instead of
.long lable_referenced_within_the_dwarf_section
. This way, when assemling one could mask out leading bits that possibly could
irritate avrstudio. However, IMO, the better way would be to teach avrstudio
simply to ignore the bits that are known to be not relevant.
Yours,
Björn
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087