This is the mail archive of the
mailing list for the GCC project.
Re: GCC 8.4 Status Report (2020-02-17)
- From: Bernd Edlinger <bernd dot edlinger at hotmail dot de>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>, Matthias Klose <doko at debian dot org>
- Date: Thu, 20 Feb 2020 13:23:28 +0000
- Subject: Re: GCC 8.4 Status Report (2020-02-17)
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7+cTo7cp8jOSAkXlucxkXYmBX50hKQY82nNZlP6cT90=; b=QKunEZhyyPFi7gcL0kJKHMEgGfPN3riQhWIldjJNT/uU5fEXRFRTFSfGJ9col9+w7qDu/8MWCXMZAR+x9JamOpBhCS5aAwhi3gAD8w8FEP/NL+0td1O4LmG2pks/3WFKtZixrtUuUh+5XExHfaN2Y85erlGp5tDciUGpHuuvJmRUSfDJjB+xPBYTQgvlcsFwDO/LZbG1YMz8q/3Gycz/JnUuKGDLUCQ33bCGeZzfGVztoF/Yz66JUCmI63lw/c1ckHyKtD1yD/qjnHgRj1aHAJ4fxtrUspCynVA1aCIIPqe2FiHQMV+aDcoH6Le3N6BUXu+duAHrsNqHdlH/U5Q7VQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=St6ubTxTVwOu5aNnvLlq4Dt5dTMl9g4OGWNUlC2IrWRJCK02LVHs+jsDrH5dR085Afpa+dH2rhqmI2sm6hUvAAkyY2Ar1Z0L4PIAz3bqDHLcbUrr3Dh8PGElhe4T+tggLYEFxAqLxf1e9fPRR3JADrblFHhDXfJlEbbVnbHuhMj5Yr3WU8jHCD4KdPIKydLG1EgvuzXWdzfoyO1xoIbhg/JtGqOXy1e/SXmoyv9A0BWv/y1ImEkzc7S54chYxkn96JbyRAN9SY9e9ogWzOczC4V1QBof0VEINWDdH+iGT8ICD2lKSmchIfyCloUzuwBaSJB6hdYHtzr0j0wON6H1sg==
- References: <AM6PR03MB51701BBBF031F11257E27273E4110@AM6PR03MB5170.eurprd03.prod.outlook.com> <CAFiYyc3Eiqo+U+o8R2Jz_e6yNh-LhnWHbHMpXGpiuH1JzFYybQ@mail.gmail.com>
On 2/19/20 10:24 AM, Richard Biener wrote:
> On Tue, Feb 18, 2020 at 8:37 PM Bernd Edlinger
> <firstname.lastname@example.org> wrote:
>>> It has been almost a year since GCC 8.3 has been released and GCC 8.4
>>> release should have been released already, so we should concentrate on
>>> getting it out soon. Unfortunately we have two P1s, one of them is
>>> waiting for reporter's input, so we might as well just ignore it unless
>>> the input is provided, but the other, C++ FE one, looks something that
>>> should be fixed. If we get rid of the P1s, I'd like to create
>>> 8.4-rc1 on Wednesday, Feb 26th and release 8.4 the week afterwards.
>>> If you have any queued backports, please commit them to 8 branch
>>> (and 9 branch too, we'd like to release 9.3 soon too).
>> Hi Jakub,
>> it just occurred to me that my patch here is a kind of
>> security relevant one:
>> since every time the collect2 process is interrupted via a signal
>> it can delete random files from the hard drive, since the
>> signal handler may be using the path name, and passes it to the unlink
>> function before it is initialized.
>> The patch doe not apply cleanly to gcc-8, but just fixing
>> that issue, without tackling the cleanup at the same time should
>> be feasible, if you like that for this version?
> Sure, these kind of fixes are always welcome, but please post them
> for review.
OK, posted here: