First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 224719
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Embedded Team <dev-embedded@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: David Barnett <daviebdawg@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
code_pack.patch code_pack.patch patch David Barnett 2008-06-03 08:15 0000 6.25 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 224719 depends on: Show dependency tree
Show dependency graph
Bug 224719 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-06-03 08:12 0000
As reported on gputils bug tracker:
gpasm produces wrong line number addresses in 18F code_pack
Consider the following source file (with line numbers prepended for
reference):

[1] radix dec
[2] processor 18F4550
[3] #include <p18f4550.inc>
[4]
[5] code_pack
[6] db 1,2,3
[7] db 4,5,6
[8] end

Compiling this source file with "gpasm -c test.asm" produces a file
"test.o". Running "gpvo test.o" produces this output:

[snipped]
Data
000000: 0201 mulwf 0x1, 0
000002: 0403 decf 0x3, 0, 0
000004: 0605 decf 0x5, 0x1, 0

Line Number Table
Line Address Symbol
6 0 test.asm
6 0x2 test.asm
7 0x4 test.asm
7 0x6 test.asm
[snipped]

Clearly the line number table is horribly wrong! In fact, as a result of
this broken line number table, gplink later crashes with an assertion
failure (lst.c:171: write_src: Assertion `data & 0x80000000' failed).

This is with 0.13.6 beta.

Reproducible: Always

------- Comment #1 From David Barnett 2008-06-03 08:15:09 0000 -------
Created an attachment (id=155337) [edit]
code_pack.patch

Patch from upstream (myself) to fix the problem.

------- Comment #2 From Denis Dupeyron 2008-06-03 08:36:31 0000 -------
Fixed. Thanks for letting us know.

Denis.

First Last Prev Next    No search results available      Search page      Enter new bug