[Starlingx-discuss] Request for clarification related to gcc 8

Wed Aug 22 14:05:02 UTC 2018

One of the reason behind exploring gcc 8 is because that is the one used in Clear Linux, as we are looking into support Clear Linux in some point in the future and we'll need to build these projects with a newer compiler. I think that this is not different from the effort to move from python 2 into python 3. 

BTW, the issue regarding the null reference is present since gcc 6, I pointed out into gcc 8 as was the first I tried. 

-Erich

On 8/22/18, 8:40 AM, "Young, Ken" <Ken.Young at windriver.com> wrote:

    Cindy,

    At a higher level, what are the plans for gcc 8?  Is this really part of the security strategy or part of moving the OS forward?  All this needs to be discussed as we kick off the work in the security group's efforts.  Right now, all the work feels adhoc.

    Regards,
    Ken Y

    On 2018-08-21, 8:23 PM, "Xie, Cindy" <cindy.xie at intel.com> wrote:

        Both shall be tagged with "stx-security" bug in my opinion.

        Thx. - cindy

        -----Original Message-----
        From: Chris Friesen [mailto:chris.friesen at windriver.com] 
        Sent: Wednesday, August 22, 2018 5:08 AM
        To: Eslimi, Dariush <Dariush.Eslimi at windriver.com>; starlingx-discuss at lists.starlingx.io
        Subject: Re: [Starlingx-discuss] Request for clarification related to gcc 8

        On 08/21/2018 01:26 PM, Eslimi, Dariush wrote:
        > If that is case Chris, then title of the bug should not be : "fm-common cannot be built with GCC 8 due to string bound checks"

        Title has been changed.  It is now:

        [Bug] GCC 8 highlights potentially-risky strncpy() usage in fm-common

        Chris

        _______________________________________________
        Starlingx-discuss mailing list
        Starlingx-discuss at lists.starlingx.io
        http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        _______________________________________________
        Starlingx-discuss mailing list
        Starlingx-discuss at lists.starlingx.io
        http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

    _______________________________________________
    Starlingx-discuss mailing list
    Starlingx-discuss at lists.starlingx.io
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss