From: valdis.kletnieks@vt.edu
To: linux-kernel@vger.kernel.org
Subject: Re: Heads up: next-20190115 and GCC 9.0 don't play nice.
Date: Sat, 26 Jan 2019 17:43:48 -0500 [thread overview]
Message-ID: <7849.1548542628@turing-police.cc.vt.edu> (raw)
In-Reply-To: <19134.1548471725@turing-police.cc.vt.edu>
On Fri, 25 Jan 2019 22:02:05 -0500, valdis.kletnieks@vt.edu said:
> So a GCC 9 escaped to Fedora Rawhide in the last few days, and things didn't
> go well. Fortunately, I had the 8.2.1-7 RPMs still around.
>
> Issue 1: There's a new warning added for taking the address of a member of
> a packed array. It wasn't *too* noisy.
>
> Issue 2: Looks like it's not ready for prime time.
Jakub Jelinek informed me that gcc-9.0.1-0.1.fc30.x86_64 was out, and
I've confirmed that *this* issue is fixed. Off to go see what breaks next. :)
prev parent reply other threads:[~2019-01-26 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 3:02 Heads up: next-20190115 and GCC 9.0 don't play nice valdis.kletnieks
2019-01-26 22:43 ` valdis.kletnieks [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=7849.1548542628@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).