public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qneill at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48743] -march=native mis-detects AMD K6-2+ / K6-3 as Athlon - compiled C fails with "illegal instruction"
Date: Mon, 19 Dec 2011 18:03:00 -0000	[thread overview]
Message-ID: <bug-48743-4-yf4wrrXJ4R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48743-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48743

--- Comment #6 from Quentin Neill <qneill at gcc dot gnu.org> 2011-12-19 17:57:42 UTC ---
Author: qneill
Date: Mon Dec 19 17:57:32 2011
New Revision: 182489

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182489
Log:
2011-12-19  Quentin Neill  <quentin.neill@amd.com>
2011-12-19  Quentin Neill  <quentin.neill@amd.com>

    PR target/48743
    * config/i386/driver-i386.c (host_detect_local_cpu): Also check
    family to distinguish PROCESSOR_ATHLON.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/driver-i386.c


  parent reply	other threads:[~2011-12-19 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 21:09 [Bug target/48743] New: " gcc.gnu.org at stellar dot eclipse.co.uk
2011-04-23 21:12 ` [Bug target/48743] " gcc.gnu.org at stellar dot eclipse.co.uk
2011-04-23 21:14 ` gcc.gnu.org at stellar dot eclipse.co.uk
2011-05-12  8:59 ` zuxy.meng at gmail dot com
2011-05-22 14:46 ` mikpe at it dot uu.se
2011-06-16 15:10 ` gcc.gnu.org at stellar dot eclipse.co.uk
2011-12-19 18:03 ` qneill at gcc dot gnu.org [this message]
2011-12-19 18:57 ` qneill at gcc dot gnu.org
2012-01-19 20:23 ` qneill at gcc dot gnu.org
2012-02-07 16:18 ` qneill at gcc dot gnu.org
2012-02-08 10:45 ` rguenth at gcc dot gnu.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=bug-48743-4-yf4wrrXJ4R@http.gcc.gnu.org/bugzilla/ \
    --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: 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).