From: Bill O'Donnell <billodo@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [XFS SUMMIT] xfs and gcc
Date: Tue, 28 Apr 2020 16:01:54 -0500 [thread overview]
Message-ID: <20200428210154.GA2060862@redhat.com> (raw)
In-Reply-To: <20200427172440.GS6742@magnolia>
On Mon, Apr 27, 2020 at 10:24:40AM -0700, Darrick J. Wong wrote:
> On Thu, Apr 23, 2020 at 10:03:06AM -0500, Bill O'Donnell wrote:
> > Hello -
> >
> > I'd be interested in having some discussion about the forward momentum
> > of gcc, and xfs staying in reasonable sync with it. I'm sure you've noticed
> > the warnings stacking up as xfs and xfsprogs is built.
To be fair, I'm only seeing a bunch of warnings on xfsprogs builds. ;)
>
> Not really, because I'm still running gcc 8.4. At least until I sort
> through the remaining grub brain damage and actually upgrade every
> system. :D
>
> > With gcc-10 coming
> > about in distros, the inevitable warnings and errors will become more than
> > annoying.
> >
> > How best to approach modifications to xfs to alleviate these build issues?
>
> No idea. :(
>
> Admittedly it would be nice to ask the kernel robot or something like it
> if it's willing to take on building some of the core userspace packages.
> They're a little spammy (we recently had a cppcheck episode) but more
> often than not, it does catch minor problems.
>
> --D
>
> > Thanks-
> > Bill
> >
>
prev parent reply other threads:[~2020-04-28 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 15:03 [XFS SUMMIT] xfs and gcc Bill O'Donnell
2020-04-27 17:24 ` Darrick J. Wong
2020-04-28 21:01 ` Bill O'Donnell [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=20200428210154.GA2060862@redhat.com \
--to=billodo@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.