From: Segher Boessenkool <segher@kernel.crashing.org>
To: Modi Mo <modimo@microsoft.com>
Cc: Nicholas Krause <xerofoify@gmail.com>,
David Malcolm <dmalcolm@redhat.com>,
Eric Gallager <egall@gwmail.gwu.edu>,
Pedro Alves <pedro@palves.net>,
Gabriel Dos Reis <gdr@microsoft.com>,
Andrew Dean <Andrew.Dean@microsoft.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"ro@CeBiTec.Uni-Bielefeld.DE"
<ro@cebitec.uni-bielefeld.de>,
"mikestump@comcast.net" <mikestump@comcast.net>,
"law@redhat.com" <law@redhat.com>,
"jason@redhat.com" <jason@redhat.com>,
Jonathan Wakely <cxx@kayari.org>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [EXTERNAL] Re: GCC selftest improvements
Date: Fri, 14 Feb 2020 23:10:00 -0000 [thread overview]
Message-ID: <20200214231036.GN22482@gate.crashing.org> (raw)
In-Reply-To: <BY5PR21MB1508456D794E4656F3329867CC1A0@BY5PR21MB1508.namprd21.prod.outlook.com>
Hi!
On Thu, Feb 13, 2020 at 10:18:27PM +0000, Modi Mo via gcc wrote:
> Segher here suggests 4.8.5 instead of 4.8.2:
> https://gcc.gnu.org/ml/gcc/2019-11/msg00192.html
I said as long as 4.8.5 works, it is fine with me. If 4.8.2 can be made
to work easily that is useful for the few people who would want to run
GCC 11 on Ubuntu 14 ("Trusty") (note this is EOL already).
> Looking at release dates 4.8.5 was in June 2015 while 4.8.2 in October 2013 which is a pretty big gap. I'd for moving the needle as far as we reasonably can since this is a leap anyways. @Segher do you have a reason in mind for the higher versioning?
It's just that that is the latest 4.8 release, and it is what I see on
all still supported systems that use 4.8.
Arnd Bergmann made a neat overview showing this (and many other things):
https://lore.kernel.org/lkml/CAK8P3a3JfUjm88CLqkvAmCoEA1FsmQ33sfHGK4=Y5iuhWxet5Q@mail.gmail.com/
Segher
next prev parent reply other threads:[~2020-02-14 23:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:50 Andrew Dean via gcc
2019-10-24 21:09 ` Jonathan Wakely
2019-10-25 6:17 ` David Malcolm
2019-10-25 22:38 ` Andrew Dean via gcc
2019-10-26 0:01 ` Gabriel Dos Reis via gcc
2019-10-26 22:46 ` Eric Gallager
2019-10-31 15:56 ` Pedro Alves
2019-12-02 2:50 ` Eric Gallager
2020-02-13 0:49 ` [EXTERNAL] " Modi Mo via gcc
2020-02-13 1:53 ` David Malcolm
2020-02-13 2:28 ` Nicholas Krause
2020-02-13 22:18 ` Modi Mo via gcc
2020-02-14 14:55 ` C++11 bootstrap (was: GCC selftest improvements) Jason Merrill
2020-02-14 23:10 ` Segher Boessenkool [this message]
2020-02-15 16:14 ` [EXTERNAL] Re: GCC selftest improvements Jeff Law
2020-02-25 19:58 ` Modi Mo via gcc
2020-02-25 22:11 ` David Malcolm
2020-02-25 22:13 ` Gabriel Dos Reis via gcc
2020-03-02 22:19 ` Modi Mo via gcc
2019-10-28 19:40 ` Jeff Law
2019-10-28 19:42 ` Richard Biener
2019-10-28 19:44 ` Jeff Law
2019-10-28 19:46 ` Gabriel Dos Reis via gcc
2019-10-28 20:27 ` Segher Boessenkool
2019-10-28 21:41 ` Jeff Law
2019-10-28 21:47 ` Jakub Jelinek
2019-10-28 21:52 ` Andrew Pinski
2019-10-28 22:02 ` Jeff Law
2019-10-28 22:03 ` Gabriel Dos Reis via gcc
2019-10-29 8:41 ` Richard Biener
2019-10-31 16:09 ` Pedro Alves
2019-10-28 21:50 ` Iain Sandoe
2019-10-28 22:12 ` Segher Boessenkool
2019-10-29 8:45 ` Richard Biener
2019-11-22 21:02 ` Andrew Dean via gcc
2019-11-22 22:02 ` Segher Boessenkool
2019-11-22 22:36 ` Jakub Jelinek
2019-11-22 23:41 ` Segher Boessenkool
2019-11-23 16:33 ` Jeff Law
2019-11-23 23:03 ` Nicholas Krause
2020-02-14 20:50 ` Mike Stump
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=20200214231036.GN22482@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Andrew.Dean@microsoft.com \
--cc=cxx@kayari.org \
--cc=dmalcolm@redhat.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc@gcc.gnu.org \
--cc=gdr@microsoft.com \
--cc=jason@redhat.com \
--cc=law@redhat.com \
--cc=mikestump@comcast.net \
--cc=modimo@microsoft.com \
--cc=pedro@palves.net \
--cc=richard.guenther@gmail.com \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=xerofoify@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).