public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pacho at condmat1 dot ciencias dot uniovi dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/45483] gcc-4.4.3: probably wrong optimization options chosen by "-march=native" Date: Wed, 01 Sep 2010 16:06:00 -0000 [thread overview] Message-ID: <20100901160624.8584.qmail@sourceware.org> (raw) In-Reply-To: <bug-45483-19637@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from pacho at condmat1 dot ciencias dot uniovi dot es 2010-09-01 16:06 ------- (In reply to comment #3) > (In reply to comment #2) > > gcc-4.5 is still hardmasked downstream in Gentoo, then, I am unsure about > > installing it :-/, are you sure this bug could be solved in 4.5* ? > > > > 1. -march=native is changed in gcc 4.5. Will try then with 4.5.1 (4.5.2 is still not available on Gentoo) > 2. Your cpu is Core. > 3. -mtune=generic generates the fastest code for Core. > 4. Prescott and Core have the same instruction set. Is -mtune=generic better than -mtune=prescott? "man gcc" looks to suggest last one would be better: If you know the CPU on which your code will run, then you should use the corresponding -mtune option instead of -mtune=generic. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45483
next prev parent reply other threads:[~2010-09-01 16:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-01 15:04 [Bug c/45483] New: " pacho at condmat1 dot ciencias dot uniovi dot es 2010-09-01 15:40 ` [Bug c/45483] " hjl dot tools at gmail dot com 2010-09-01 15:51 ` pacho at condmat1 dot ciencias dot uniovi dot es 2010-09-01 15:56 ` [Bug target/45483] " hjl dot tools at gmail dot com 2010-09-01 16:06 ` pacho at condmat1 dot ciencias dot uniovi dot es [this message] 2010-09-01 16:37 ` hjl dot tools at gmail dot com 2010-09-06 10:45 ` pacho at condmat1 dot ciencias dot uniovi dot es 2010-09-06 15:09 ` hjl dot tools at gmail dot com [not found] <bug-45483-4@http.gcc.gnu.org/bugzilla/> 2011-09-22 20:49 ` pacho at condmat1 dot ciencias.uniovi.es
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=20100901160624.8584.qmail@sourceware.org \ --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: 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).