public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: BAN Nobuhiro <ban@localhost.ipl.t.u-tokyo.ac.jp>
To: gcc-gnats@gcc.gnu.org
Subject: c/9678: Incorrect specs for cpp_cpucommon on i386
Date: Wed, 12 Feb 2003 21:56:00 -0000	[thread overview]
Message-ID: <200302122148.h1CLm3Ej098139@localhost.ipl.t.u-tokyo.ac.jp> (raw)


>Number:         9678
>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:   Wed Feb 12 21:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     BAN Nobuhiro
>Release:        3.2.2
>Organization:
>Environment:
i386
>Description:
    ``gcc -march=pentium2'' does not give some options
(``-D__pentium2 -D__pentium2__'') to cc1.
>How-To-Repeat:
    % gcc -march=pentium2 -v --help
    % gcc -march=march=pentium2 -v --help
>Fix:
    Aapply this:

--- gcc-3.2.2/gcc/config/i386/i386.h.orig	Tue Dec 10 09:40:11 2002
+++ gcc-3.2.2/gcc/config/i386/i386.h	Thu Feb 13 06:44:47 2003
@@ -587,7 +587,7 @@
 %{march=pentiumpro|march=i686|march=pentium2|march=pentium3:-D__i686 -D__i686__ \
   -D__pentiumpro -D__pentiumpro__ \
   %{!mcpu*:-D__tune_i686__ -D__tune_pentiumpro__ }}\
-%{march=march=pentium2|march=pentium3: -D__pentium2 -D__pentium2__\
+%{march=pentium2|march=pentium3: -D__pentium2 -D__pentium2__\
   %{!mcpu*:-D__tune_pentium2__ }}\
 %{march=pentium3: -D__pentium3 -D__pentium3__\
   %{!mcpu*:-D__tune_pentium3__ }}\
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-02-12 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 21:56 BAN Nobuhiro [this message]
2003-02-20  8:44 ebotcazou
2003-02-20 20:15 ebotcazou

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=200302122148.h1CLm3Ej098139@localhost.ipl.t.u-tokyo.ac.jp \
    --to=ban@localhost.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: 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).