bug-binutils
[Top][All Lists]
Advanced

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

[Bug gold/16804] gold rejects kernel linker script


From: cvs-commit at gcc dot gnu.org
Subject: [Bug gold/16804] gold rejects kernel linker script
Date: Fri, 04 Apr 2014 16:29:52 +0000

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

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  abc9061b5c4d684da66945a9928d54a424cb6e4e (commit)
      from  2cf200a4c8a850e6f696e572ea03f340eae97c8a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

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

commit abc9061b5c4d684da66945a9928d54a424cb6e4e
Author: Cary Coutant <address@hidden>
Date:   Fri Apr 4 09:28:23 2014 -0700

    Document optional comma in linker script.

    The linker script documentation does not mention the optional comma
    that may follow an output section command or an overlay command.
    In some cases, where a fill expression is used, and the next
    output section command begins with an operator (e.g., "/DISCARD/"),
    the comma may be required to separate the two commands.

    Currently, GNU ld doesn't require the comma, but gold does.

    ld/
        PR gold/16804
        * ld.texinfo: Document optional comma following output section
        command and overlay command.

-----------------------------------------------------------------------

Summary of changes:
 ld/ChangeLog  |    6 ++++++
 ld/ld.texinfo |    9 +++++++--
 2 files changed, 13 insertions(+), 2 deletions(-)

-- 
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]