From: Richard Biener <richard.guenther@gmail.com>
To: Vanida Plamondon <vanida.plamondon@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Ryzen PPA znver1 optimizations
Date: Fri, 08 Mar 2019 11:00:00 -0000 [thread overview]
Message-ID: <CAFiYyc2Yqh8mUukbK1V9P-wt0Pc58+vNKBZUi93irzNmY7JftQ@mail.gmail.com> (raw)
In-Reply-To: <CAMm9xBzrVLzOmBuxEGNrDi0E7ExOsEoAdLs9eFetgw_J_bP2pQ@mail.gmail.com>
On Fri, Mar 8, 2019 at 8:56 AM Vanida Plamondon
<vanida.plamondon@gmail.com> wrote:
>
> I have been working on some PPA's that will provide standard Ubuntu
> and Linux Mint packages that are compiled with the znver1 cpu
> optimisations (Ryzen CPU). It has been quite tedious (though not
> particularly hard) to modify existing packages to be compiled with
> "-march=znver1" cflags and cxxflags, and since I started creating a
> toolchain to make the builds in the PPAs compile more reliably while
> producing broken less packages, I decided to modify GCC to always spit
> out ryzen optimised code automatically regardless of what code is
> thrown at it.
>
> I changed each instance of =generic in gcc/config.gcc to =znver1, and
> each instance of cpu=<something> to cpu=znver1, and each instance of
> arch=<something> that wasn't i386, i486, i586, i686, i786, x86-64, or
> x86_64 to arch=znver1.
You can configure with --with-arch=znver1 --with-tune=znver1 to
achieve the same effect.
> So what I think will happen is that I will set a PPA with a dependency
> on the PPA with the modified GCC, and any package I upload/copy to the
> aforementioned PPA that is compiling to x86 code will compile as
> though I set the "-march=znver1" option. Does anyone know whether or
> not this is going to work the way I think it will, or know how I can
> test to see if such is the case with the resulting binary packages?
>
> Also, is there a better way to do what I am trying to do?
next prev parent reply other threads:[~2019-03-08 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 7:56 Vanida Plamondon
2019-03-08 11:00 ` Richard Biener [this message]
2019-03-08 11:28 ` Vanida Plamondon
2019-03-08 20:58 ` Jonathan Wakely
2019-03-08 22:00 ` Vanida Plamondon
2019-03-08 22:44 ` Jonathan Wakely
2019-03-08 22:59 ` Vanida Plamondon
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=CAFiYyc2Yqh8mUukbK1V9P-wt0Pc58+vNKBZUi93irzNmY7JftQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=vanida.plamondon@gmail.com \
/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).