Date: Mon, 30 Jul 2001 18:12:46 +0100 (BST) From: Steve Roome <steve@semtexforsale.co.uk> To: FreeBSD-gnats-submit@freebsd.org Subject: gnu/29331: still documented broken options in gcc manpage Message-ID: <200107301712.f6UHCkL08943@mail.yahoo.com>
next in thread | raw e-mail | index | archive | help
>Number: 29331 >Category: gnu >Synopsis: still documented broken options in gcc manpage >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Jul 30 10:30:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Steve Roome >Release: FreeBSD 4.3-RELEASE i386 >Organization: >Environment: System: FreeBSD dylan.home 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Fri Jul 20 15:16:40 BST 2001 steve@dylan.home:/usr/src/sys/compile/PEPCROSS i386 >Description: gcc still has -mno-move option documented in the manpage but if you view the GCC GNATS database (PR optimization/496) you'll see that it should not still be documented as it's apparently not a working option. Beside the manpage doesn't explain what it does anyway. Until the gcc folks get around to fixing their compiler to not accept broken options should we remove the offending -mno-move option from the manpage (a small patch to the 4.3-RELEASE manpage is supplied) >How-To-Repeat: man gcc >Fix: Here's a patch to the gcc.1 manpage (it's a patch against an uncompressed /usr/share/man/en.ISO_8859-1/man1/gcc.1.gz) --- gcc.1 Mon Jul 30 18:07:18 2001 +++ gcc.1.orig Mon Jul 30 18:06:14 2001 @@ -463,6 +463,7 @@ \-mfancy\-math\-387 \-mno\-wide\-multiply \-mdebug\-addr +\-mno\-move \-mprofiler\-epilogue \-reg\-alloc=LIST .Sp >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107301712.f6UHCkL08943>