--- Additional Comments From nickc at redhat dot com 2006-07-11 14:13
---
Hi Bill,
Why not simply post-process the memory map. There are lots of text handling
tools that can do this, so why add extra code to the linker. It just introduces
more places for bugs to occur and adds compl
When I accidentally assembled 32-bit assembly source with 64-bit assembler, I
got an internal error. This effectively boils down to following test case:
$ x86_64-elf64-linux-as
movl $_GLOBAL_OFFSET_TABLE_, %eax
^D^D
{standard input}: Assembler messages:
{standard input}:1: Internal error, aborting
--
What|Removed |Added
Priority|P1 |P3
http://sourceware.org/bugzilla/show_bug.cgi?id=2904
--- You are receiving this mail because: ---
Y
gas 2.14 and 2.16 can SEGV trying to report an error
assembling this erroneous code:
.set bar,5f+text1
5:
text1:
The bug is that 'report_op_error' incorrectly uses 'file' and 'line'
in the 'else' case where they are not initialized. Because the value
of 'file' is garbage, it is of course
