From: Matt Connell <matt@connell.tech>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: repair of a seg-faulting bin-utils
Date: Wed, 26 Oct 2022 14:45:09 -0400 [thread overview]
Message-ID: <61c1b37ffb962213c5ca0cce5fca3429f17f6bf2.camel@connell.tech> (raw)
In-Reply-To: <CAGfcS_=xS1JMWjdwfQ=PgYyNKqt8zgYQZssUa_EDTXyYLyvqWg@mail.gmail.com>
On Wed, 2022-10-26 at 14:37 -0400, Rich Freeman wrote:
> Another possible issue is bad -march settings. That usually is an
> issue if you change your CPU and boot off of an existing hard drive.
> If you're going to upgrade your CPU you should rebuild all of @system
> (at least) with -march set to something very minimal. Don't assume
> that a newer CPU does everything an existing one does - they sometimes
> do drop instructions. You can set -mcpu to whatever you want, as a
> bad -mcpu will only cause minor performance issues.
Further reading on this:
https://wiki.gentoo.org/wiki/Safe_CFLAGS
I've always used this as a reference for helping ensure make.conf is
not only going to be well optimized, but produce reliable binaries.
prev parent reply other threads:[~2022-10-26 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 16:14 [gentoo-user] repair of a seg-faulting bin-utils Corbin
2022-10-26 16:24 ` [gentoo-user] " Grant Edwards
2022-10-26 18:37 ` Rich Freeman
2022-10-26 18:45 ` Matt Connell [this message]
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=61c1b37ffb962213c5ca0cce5fca3429f17f6bf2.camel@connell.tech \
--to=matt@connell.tech \
--cc=gentoo-user@lists.gentoo.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