From: Richard Biener <richard.guenther@gmail.com>
To: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCHv2] debug: make -feliminate-unused-debug-symbols the default [PR debug/86964]
Date: Fri, 31 May 2019 09:23:00 -0000 [thread overview]
Message-ID: <CAFiYyc1c2mxMcKMY12Qq-G6K9MWSdD9udxQe6eNomnLU11KxrQ@mail.gmail.com> (raw)
In-Reply-To: <CAAXf6LXU37VdwuZ_rN=3L=oqWULR1pdSZr14AJp1CT87dg4mQA@mail.gmail.com>
On Fri, May 31, 2019 at 10:39 AM Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
>
>
>
> On Fri, May 31, 2019, 10:23 Richard Biener <richard.guenther@gmail.com> wrote:
>>
>> On Wed, May 29, 2019 at 12:10 PM Thomas De Schampheleire
>> <patrickdepinguin@gmail.com> wrote:
>> >
>> > Hi Richard,
>>
>> Sorry for the delay - I have bootstrapped/tested the patch and
>> installed it on trunk.
>> If there will be no complaints I plan to backport it for GCC 9.2 (you
>> may need to
>> remind me in a few weeks).
>
>
> Thanks.
>
> I think I read somewhere that 7.4 is the last 7.x release, is that correct?
>
> But what about 8.x? If there will be a new release I think these patches should be backported too, no? After all, it's part of a regression.
I'm not opposed to that but would like to see feedback first - too bad
we missed making this the default for GCC 9.1.
> In what location can you see such info about which branches and releases are expected, latest release in a stream, etc?
There's only the toplevel https://gcc.gnu.org/ page which lists active
branches. That the next release from the 7 branch will be
the last is not documented anywhere.
Richard.
> Best regards
> Thomas
prev parent reply other threads:[~2019-05-31 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 14:58 Thomas De Schampheleire
2019-05-29 10:55 ` Thomas De Schampheleire
2019-05-31 8:39 ` Richard Biener
2019-05-31 8:50 ` Thomas De Schampheleire
2019-05-31 9:23 ` Richard Biener [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=CAFiYyc1c2mxMcKMY12Qq-G6K9MWSdD9udxQe6eNomnLU11KxrQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=patrickdepinguin@gmail.com \
--cc=thomas.de_schampheleire@nokia.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).