public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jc at apinc dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/15858] New: gnatelim still referenced in the GNAT user and reference manuals
Date: Mon, 07 Jun 2004 14:28:00 -0000	[thread overview]
Message-ID: <20040607142848.15858.jc@apinc.org> (raw)

gnatelim doesn't seem to be generated anymore in the lasts gcc versions.
However its documentation is still present in the documentation.
There are also small references to gnatelim in the comments of gnatcmd.adb, 
and gnatelim is still considered as a valid command in vms_conv.adb.

An easy replacement of gnatelim is made with the parameters -ffunction-sections 
and -fdata-sections during compilation, and -gc-sections during the linking 
stage. So it might be a replacement in the documentation.

I could do a patch myself, but you would probably be affraid by my english. 
Nevertheless if it's just deleting the gnatelim sections in the doc, I obviously 
can do it, if it helps.

Regards,
JC

-- 
           Summary: gnatelim still referenced in the GNAT user and reference
                    manuals
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jc at apinc dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: N/A
  GCC host triplet: N/A
GCC target triplet: N/A


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15858


             reply	other threads:[~2004-06-07 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 14:28 jc at apinc dot org [this message]
2004-06-07 15:13 ` [Bug ada/15858] " pinskia at gcc dot gnu dot org

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=20040607142848.15858.jc@apinc.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).