From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Mark Butt <mark@markwbutt.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
gcc-help@gcc.gnu.org
Subject: Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
Date: Fri, 27 Jan 2023 11:58:45 -0600 [thread overview]
Message-ID: <20230127175845.GQ25951@gate.crashing.org> (raw)
In-Reply-To: <0a2e72ff-e0ce-f413-aeeb-1bdb1cfbd512@gmail.com>
On Sun, Jan 22, 2023 at 11:40:46AM -0700, Jeff Law via Gcc-help wrote:
> On 1/22/23 10:37, Mark Butt wrote:
> >No, there is no reason to be at 8.3.0 other than this was the minimum
> >required. I thought that I might have better luck getting 8.3 to work vs
> >a newer version given the age of the hardware, I will, however, try a
> >newer version as suggested.
> >
> >Would you recommend going with a particular version or just get the latest
> >and greatest?
> I'd just go with the latest release. You could go with one of the
> weekly development snapshots, but that may introduce problems you don't
> want to deal with.
Yes. And some things that have been fixed in the newest release series
have not been fixed in older ones, for various reasons (too dangerous,
too difficult, compared with expected benefit). And nothing is fixed
anymore in release series that have reached end of life of course (so
everything before GCC 10, currently).
If you have no particular reason to want something older (or newer), use
the latest released version? That is GCC 12.2 now. The main reason to
use an older release series is if you already were using it :-)
Segher
next prev parent reply other threads:[~2023-01-27 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:40 Mark Butt
2023-01-20 17:30 ` Jonathan Wakely
2023-01-22 17:37 ` Mark Butt
2023-01-22 18:36 ` Jonathan Wakely
2023-01-22 18:40 ` Jeff Law
2023-01-27 17:58 ` Segher Boessenkool [this message]
2023-01-27 19:21 ` Mark Butt
2023-01-27 19:25 ` Arsen Arsenović
2023-01-27 20:17 ` Jonathan Wakely
2023-01-27 21:14 ` Segher Boessenkool
2023-01-27 19:41 ` Christer Solskogen
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=20230127175845.GQ25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jwakely.gcc@gmail.com \
--cc=mark@markwbutt.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).