public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mahatma at eu dot by" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45359] poor -march=native choices for VIA C7 Esther processors
Date: Mon, 01 Nov 2010 13:21:00 -0000	[thread overview]
Message-ID: <20101101132100.pSixcMkte7uyczMmwm3CBeeUC5Vc9xAt5nZsXMOS5U8@z> (raw)
In-Reply-To: <bug-45359-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Dzianis Kahanovich <mahatma at eu dot by> 2010-11-01 13:21:40 UTC ---
Created attachment 22220
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22220
native VIA/CentaurHauls

(In reply to comment #1)
> Why do you think it's a poor choice?

This is regression after PR target/44046. Previous behaviour was:
sse3 -> "-march=prescott -mtune=generic", now: sse3 -> "-march=pentium-m
-mtune=generic". This regression lose sse3 support for C-7 CPU. But in other
point, "prescott" as family-15 member, may be (or not) else scheduled, then
family-6 clone... Other source of problem - VIA/Centaur CPUs detecting as
"Intel" vendor. I believe, Intel support have own reason to make choice sse3 ->
pentium-m and lose this sse3, then I suggest to forget this behaviour and add
native VIA/CentaurHauls support code. There are 3 point of detection:
1) vendor signature;
2) cache detection: according to Linux kernel code,  "detect_caches_amd"
behaviour is not vendor-specific and used in kernel also for any x86_64,
VIA/Centaur, Transmeta and Cyrix family-5/model-5, but I have no exotic CPUs
exclude VIA C-7 in my notebook to test other vendors;
3) model detection - C-7 will be "-march=prescott -mtune=core2" (FIXME if pure
"prescott" is better!), also may be fixed c3-2 -mtune=c3 selection (Gentoo Wiki
suggest -mtune=generic or -march=c3 to avoid NOPL for some models, but I try to
not use variable "generic").


       reply	other threads:[~2010-11-01 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45359-4@http.gcc.gnu.org/bugzilla/>
2010-11-01 13:21 ` mahatma at eu dot by [this message]
2010-11-07 10:47 ` mahatma at eu dot by
2010-11-18 13:10 ` mahatma at eu dot by
2013-04-25 19:07 ` linuxball at netscape dot net
2013-05-17 18:00 ` ubizjak at gmail dot com
2010-08-20 15:58 [Bug target/45359] New: " opod at nic-nac-project dot org
2010-08-23 20:17 ` [Bug target/45359] " rguenth at gcc dot gnu dot org
2010-08-24 18:59 ` opod at nic-nac-project 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=20101101132100.pSixcMkte7uyczMmwm3CBeeUC5Vc9xAt5nZsXMOS5U8@z \
    --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).