public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: fshahbazker@wavecomp.com
To: binutils@sourceware.org
Subject: [RFC] [PATCH] ld: Add --no-print-map-discarded option
Date: Fri, 27 Jul 2018 16:03:00 -0000	[thread overview]
Message-ID: <1532707360-31871-1-git-send-email-fshahbazker@wavecomp.com> (raw)

Hi,

This patch introduces an option to disable the listing of discarded sections
in map file output. The use case stems from a largeish application built with
-ffunction-sections & --gc-sections where the list of discarded sections
blows up the map file output. The default behaviour will ofcourse remain
to print discarded sections, but the new option would allow us to disable it.

Comments welcome.

Regards,
Faraz Shahbazker

Faraz Shahbazker (1):
  ld: Add --no-print-map-discarded option

 ld/ld.h                                   |  3 +++
 ld/ldlang.c                               | 25 +++++++++++++------------
 ld/ldlex.h                                |  2 ++
 ld/ldmain.c                               |  1 +
 ld/lexsup.c                               | 12 ++++++++++++
 ld/testsuite/ld-gc/gc.exp                 |  2 ++
 ld/testsuite/ld-gc/skip-map-discarded.d   |  3 +++
 ld/testsuite/ld-gc/skip-map-discarded.map |  5 +++++
 ld/testsuite/ld-gc/skip-map-discarded.s   |  5 +++++
 9 files changed, 46 insertions(+), 12 deletions(-)
 create mode 100644 ld/testsuite/ld-gc/skip-map-discarded.d
 create mode 100644 ld/testsuite/ld-gc/skip-map-discarded.map
 create mode 100644 ld/testsuite/ld-gc/skip-map-discarded.s

-- 
2.7.4

             reply	other threads:[~2018-07-27 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 16:03 fshahbazker [this message]
2018-08-01 14:56 ` Nick Clifton
2018-08-01 15:04   ` Faraz Shahbazker
2018-08-01 16:01     ` Nick Clifton
2019-04-02 19:58       ` [PATCH v2] " Faraz Shahbazker
2019-04-02 20:17       ` [PATCH v3] " Faraz Shahbazker
2019-04-10 15:57         ` Nick Clifton
2019-04-10 16:19           ` Faraz Shahbazker
2019-04-11 10:54             ` Nick Clifton
2019-04-11 14:05               ` Faraz Shahbazker
2018-07-27 16:53 [RFC] [PATCH] " fshahbazker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1532707360-31871-1-git-send-email-fshahbazker@wavecomp.com \
    --to=fshahbazker@wavecomp.com \
    --cc=binutils@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).