public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linuxball at netscape dot net" <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: Thu, 25 Apr 2013 19:07:00 -0000	[thread overview]
Message-ID: <bug-45359-4-2oD9gPNhku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45359-4@http.gcc.gnu.org/bugzilla/>


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

linuxball at netscape dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |linuxball at netscape dot
                   |                            |net

--- Comment #6 from linuxball at netscape dot net 2013-04-25 19:07:45 UTC ---
I reconfirm this bug using gcc 4.6.3-1ubuntu5 in Ubuntu 12.04 to compile stuff
optimized for VIA C7-D Esther processor. Still the same issue:

Using -march=native 

1) still chooses -march=pentium-m -mtune=generic (ignoring the sse3 capability)
2) will not detect the L1 and L2 cache parameters

IMHO, the centaur2.patch suggested by Dzianis Kahanovich is a good fix. Why
hasn't it found its way into the official gcc?

Best regards and thanks to Dzianis for his contribution

linuxball


  parent reply	other threads:[~2013-04-25 19:07 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
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 [this message]
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=bug-45359-4-2oD9gPNhku@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).