public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ban@ipl.t.u-tokyo.ac.jp To: gcc-gnats@gcc.gnu.org Subject: c/7242: Incorrect specs for cpp_cpucommon on i386 Date: Tue, 09 Jul 2002 06:56:00 -0000 [thread overview] Message-ID: <200207091353.g69DrTA47088@localhost.ipl.t.u-tokyo.ac.jp> (raw) >Number: 7242 >Category: c >Synopsis: Incorrect specs for cpp_cpucommon on i386 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jul 09 06:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: BAN Nobuhiro >Release: 3.1.1 20020701 (prerelease) [FreeBSD] >Organization: >Environment: i386 >Description: ``gcc -mcpu=pentium[23]'' invokes cc1 without ``-D__tune_pentiumpro__'' >How-To-Repeat: % gcc -mcpu=pentium3 -v --help or % gcc -mcpu=pentium2 -v --help shows what options are given for cc1. >Fix: Replace gcc/config/i386/i386.h with the output of: % sed 's/\|cpu=pentium2\|cpu=pentium3/\|mcpu=pentium2\|mcpu=pentium3/' gcc/config/i386/i386.h >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-09 13:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-09 6:56 ban [this message] 2002-07-22 13:13 neil 2002-10-03 10:43 hubicka
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=200207091353.g69DrTA47088@localhost.ipl.t.u-tokyo.ac.jp \ --to=ban@ipl.t.u-tokyo.ac.jp \ --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).