All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Chang <mchang@suse.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: gcc9.1 and f2fs
Date: Fri, 17 May 2019 15:31:00 +0800	[thread overview]
Message-ID: <20190517073100.GD31228@mazu> (raw)
In-Reply-To: <CAFbqK8=qbRG_3quHAjyKee6+ULMU0k1ovTt2AwSGp=gRCPaotg@mail.gmail.com>

On Wed, May 08, 2019 at 01:51:20AM +0100, Neil MacLeod wrote:
> Adrian
> 
> I used the attached patch and grub is now building for me with gcc-9.1.
> 
> I've no idea if this is the right solution, but it does at least work
> (ie. builds) which is all I require for now as I'm not personally
> using grub in the distribution I'm building (LibreELEC) and can't
> actually say if it works at run-time.

Hi Neil,

The gcc diagnose here is right and addressed a real problem IMHO, so we
can't suppress it but have to fix the real problem it has pointed out.

I will try to come up with a patch and post it to mailing list.

Thanks,
Michael

> 
> Many thanks
> Neil
> 
> 
> On Mon, 6 May 2019 at 20:58, Neil MacLeod <neil@nmacleod.com> wrote:
> >
> > Hi Adrian
> >
> > With your patch, grub now fails to build as follows:
> >
> > fs/f2fs.c: In function 'grub_f2fs_get_block':
> > fs/f2fs.c:864:43: error: 'offset' may be used uninitialized in this
> > function [-Werror=maybe-uninitialized]
> >   864 |     return grub_le_to_cpu32 (inode->i_addr[offset[0]]);
> >       |                                           ^
> > cc1: all warnings being treated as errors
> > make[4]: *** [Makefile:33773: fs/f2fs_module-f2fs.o] Error 1
> >
> > This is the last 1000 lines of the build log with your patch applied:
> > http://ix.io/1IfE
> >
> > And this is the f2fs.c used for the compilation (it includes your
> > patch): http://ix.io/1IfC
> >
> > Many thanks
> > Neil
> >
> > On Mon, 6 May 2019 at 19:19, Neil MacLeod <neil@nmacleod.com> wrote:
> > >
> > > Thanks Adrian - testing with your patch now, will be another hour or
> > > so until the build is complete (cross-compiling environment with own
> > > toolchain etc.)
> > >
> > > Just a correction, I'm testing with
> > > 4dd4ceec023111a4ccf69f8de6fa0885c6847a35 (current HEAD) - looks like I
> > > cut & pasted a rev from a different repo in my original post!
> > >
> > > Regards
> > > Neil
> > >
> > > On Mon, 6 May 2019 at 18:59, John Paul Adrian Glaubitz
> > > <glaubitz@physik.fu-berlin.de> wrote:
> > > >
> > > > On 5/6/19 7:15 PM, Neil MacLeod wrote:
> > > > > Does anyone have a patch?
> > > >
> > > > Try the attached patch.
> > > >
> > > > Adrian
> > > >
> > > > --
> > > >  .''`.  John Paul Adrian Glaubitz
> > > > : :' :  Debian Developer - glaubitz@debian.org
> > > > `. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
> > > >   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



  parent reply	other threads:[~2019-05-17  7:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 17:15 gcc9.1 and f2fs Neil MacLeod
2019-05-06 17:31 ` Bruce Dubbs
2019-05-06 17:36   ` Neil MacLeod
2019-05-06 17:59 ` John Paul Adrian Glaubitz
2019-05-06 18:19   ` Neil MacLeod
2019-05-06 19:58     ` Neil MacLeod
2019-05-08  0:51       ` Neil MacLeod
2019-05-08  1:09         ` Neil MacLeod
2019-05-10 10:56           ` Daniel Kiper
2019-05-17  7:31         ` Michael Chang [this message]
2019-05-17  7:13   ` Michael Chang
2019-05-17  9:03     ` John Paul Adrian Glaubitz
2019-05-17 17:12     ` Bruce Dubbs
2019-05-20 11:55       ` Daniel Kiper

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=20190517073100.GD31228@mazu \
    --to=mchang@suse.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=grub-devel@gnu.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.