public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhgutteridge at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/23644] New: IA-64 hardware models and configuration options documentation error for 3.4.x and 4.0.x Date: Tue, 30 Aug 2005 21:36:00 -0000 [thread overview] Message-ID: <20050830211902.23644.dhgutteridge@hotmail.com> (raw) Hello, I've filed this under web, though obviously it applies to your info pages as well, I assume you generate everything from the same source, so this may be better filed somewhere else. (How come you don't have a documentation component to choose for bug reports?) For both gcc 3.4(.4) and 4.0(.1), under IA-64 options, your documentation states: "-mtune-arch=cpu-type Tune the instruction scheduling for a particular CPU, Valid values are itanium, itanium1, merced, itanium2, and mckinley." The correct option is specified as -mtune=cpu-type, as is noted here (under the IA-64 heading): http://gcc.gnu.org/gcc-3.4/changes.html "Tuning code for the Itanium 2 processor has been added. The generation of code tuned for Itanium 2 (option -mtune=itanium2) is enabled by default now. To generate code tuned for Itanium 1 the option -mtune=itanium1 should be used." Regards, David H. Gutteridge -- Summary: IA-64 hardware models and configuration options documentation error for 3.4.x and 4.0.x Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: web AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dhgutteridge at hotmail dot com 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=23644
next reply other threads:[~2005-08-30 21:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-30 21:36 dhgutteridge at hotmail dot com [this message] 2005-08-30 22:11 ` [Bug target/23644] " 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=20050830211902.23644.dhgutteridge@hotmail.com \ --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: 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).