bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/25828] nm for pdp11-aout shows symbols undefined or sign-e


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/25828] nm for pdp11-aout shows symbols undefined or sign-extended to 64 bits
Date: Mon, 20 Apr 2020 11:50:50 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=25828

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Nick Clifton <address@hidden>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=23c8270e9dc60bb78c1800b7deedc117efdb9e92

commit 23c8270e9dc60bb78c1800b7deedc117efdb9e92
Author: Stephen Casner <address@hidden>
Date:   Mon Apr 20 12:49:50 2020 +0100

    When bfd/pdp11.c was copied from bfd/aoutx.h, the #defines for external
symbol types N_TEXT etc. were #undef'd and then #define'd with new values.  But
N_STAB was not changed even though the new value for N_EXT overlapped with it. 
This caused aout_link_write_symbols() to treat global symbols referenced in the
source but defined in a linker script as undefined.

    Separately, in translate_symbol_table() the 16-bit symbol values were sign
extended to unsigned long (e.g., 64 bits) when they really should be treated as
unsigned so the value remains 16 bits.

            PR 25828
            * pdp11.c (N_STAB): Modify value to avoid conflict with N_EXT
            causing globals from linker script to be treated as debug symbols.
            (translate_symbol_table): Don't sign-extend symbol values from 16
            to 64 bits in nm output.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]