public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jost Martin <Martin.Jost@icn.siemens.de> To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org> Subject: other/7549: gcc3.1: Documentation glitches in info-files Date: Fri, 09 Aug 2002 04:46:00 -0000 [thread overview] Message-ID: <495C6C4DAAD7D2119ADF0008C71EEF3F0135031D@MCHH229E> (raw) >Number: 7549 >Category: other >Synopsis: gcc3.1: Documentation glitches in info-files >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Fri Aug 09 03:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: >Release: 3.1 >Organization: >Environment: System: HP-UX lasagne B.10.20 U 9000/785 2007890687 unlimited-user = license host: hppa1.1-hp-hpux10.20 build: hppa1.1-hp-hpux10.20 target: hppa1.1-hp-hpux10.20 configured with: ../gcc-3.1/configure -prefix=3D/pd/gcc-3.1 = --with-gnu-as --with-as=3D/pd/binutils/bin/as = --host=3Dhppa1.1-hp-hpux10.20 --without-gnu-ld >Description: I stumbled over some documentation glitches in the info-files: Warning options: "-Wall switches on a whole bunch of -W...-Options." Unfortunately, the info-page only mentions this at the end of the list. (At that point I already had hand-added all those options, just to discard them again because this was redundant and clobbered the cmd-line...) "Options That Control Optimization" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D ... `-ftrapv' This option generates traps for signed overflow on addition, subtraction, multiplication operations. Huh ?! I guess this will make the program slower (because of the checks) but better checked. So why is this listed under 'Optimization' ?? Shouldn't this be included under another section ?? " `-ffunction-sections' `-fdata-sections' Place each function or data item into its own section in the = output file if the target supports arbitrary sections. The name of the function or the name of the data item determines the section's = name in the output file. Use these options on systems where the linker can perform optimizations to improve locality of reference in the instruction space. HPPA processors running HP-UX and Sparc processors running Solaris 2 have linkers with such optimizations. Other systems using the ELF object format as well as AIX may have these optimizations in the future. " I'm using gcc on HPUX 10.20 (HPPA) Nevertheless I get: cc1plus: warning: -ffunction-sections not supported for this target cc1plus: warning: -fdata-sections not supported for this target >How-To-Repeat: >Fix: ------------------------------------------------------------------------= ----- Martin Jost Tel.: ++49/89/722-44248 Siemens AG FAX.: ++49/89/722-53418 ICN WN OP TDC TC 2 (Please note my name on the FAX !) Hofmannstr. 51 Room 1714-560 D-81359 M=FCnchen Martin.Jost@icn.siemens.de >Release-Note: >Audit-Trail: >Unformatted: X-send-pr-version: 3.113 X-GNATS-Notify:
reply other threads:[~2002-08-09 10:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=495C6C4DAAD7D2119ADF0008C71EEF3F0135031D@MCHH229E \ --to=martin.jost@icn.siemens.de \ --cc=gcc-gnats@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: linkBe 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).