Correct. It's hard to nail down the right terminology when I'm learning by
doing. I want GCC to ignore x86 flags that aren't znver1, and keep znver1
as the default.
On Fri, Mar 8, 2019, 3:44 PM Jonathan Wakely wrote:
> On Fri, 8 Mar 2019 at 22:00, Vanida Plamondon
> wro
better way, I need an
explanation so I know if the proposed solution is going to work the
way I want.
On Fri, Mar 8, 2019 at 1:58 PM Jonathan Wakely wrote:
>
> On Fri, 8 Mar 2019 at 11:28, Vanida Plamondon
> wrote:
> >
> > I realise that, however, debian packages seem
config.gcc modification works as I
don't know if it works the way I think it works, and I haven't figured
out how to test the packages I have compiled with gcc.
On Fri, Mar 8, 2019 at 4:00 AM Richard Biener
wrote:
>
> On Fri, Mar 8, 2019 at 8:56 AM Vanida Plamondon
> 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,
