All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Build regressions/improvements in v5.18-rc1
Date: Mon, 4 Apr 2022 12:19:39 +0200	[thread overview]
Message-ID: <CAMuHMdWgqdR1o3wT9pjB=w8z=2xaDFv5DJX58-HPHOFRm3Tr8Q@mail.gmail.com> (raw)
In-Reply-To: <20220404092655.GR1544202@dread.disaster.area>

Hi Dave

CC Arnd

On Mon, Apr 4, 2022 at 11:27 AM Dave Chinner <david@fromorbit.com> wrote:
> On Mon, Apr 04, 2022 at 10:16:08AM +0200, Geert Uytterhoeven wrote:
> > On Mon, 4 Apr 2022, Geert Uytterhoeven wrote:
> > > Below is the list of build error/warning regressions/improvements in
> > > v5.18-rc1[1] compared to v5.17[2].
> > >
> > > Summarized:
> > >  - build errors: +36/-15
> > >  - build warnings: +5/-38
> > >
> > > Happy fixing! ;-)
>
> Well....
>
> > >  + /kisskb/src/fs/xfs/xfs_buf.h: error: initializer element is not constant:  => 46:23
>
> Looking at:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/14714961/
>
> The build error is:
>
> /kisskb/src/fs/xfs/./xfs_trace.h:432:2: note: in expansion of macro 'TP_printk'
>   TP_printk("dev %d:%d daddr 0x%llx bbcount 0x%x hold %d pincount %d "
>   ^
> /kisskb/src/fs/xfs/./xfs_trace.h:440:5: note: in expansion of macro '__print_flags'
>      __print_flags(__entry->flags, "|", XFS_BUF_FLAGS),
>      ^
> /kisskb/src/fs/xfs/xfs_buf.h:67:4: note: in expansion of macro 'XBF_UNMAPPED'
>   { XBF_UNMAPPED,  "UNMAPPED" }
>     ^
> /kisskb/src/fs/xfs/./xfs_trace.h:440:40: note: in expansion of macro 'XFS_BUF_FLAGS'
>      __print_flags(__entry->flags, "|", XFS_BUF_FLAGS),
>                                         ^
> /kisskb/src/fs/xfs/./xfs_trace.h: In function 'trace_raw_output_xfs_buf_flags_class':
> /kisskb/src/fs/xfs/xfs_buf.h:46:23: error: initializer element is not constant
>  #define XBF_UNMAPPED  (1 << 31)/* do not map the buffer */
>
> This doesn't make a whole lotta sense to me. It's blown up in a
> tracepoint macro in XFS that was not changed at all in 5.18-rc1, nor
> was any of the surrounding XFS code or contexts.  Perhaps something
> outside XFS changed to cause this on these platforms?

Upon closer look, all builds showing this issue are using gcc-5...

> Can you bisect this, please?

Fortunately I still have gcc-5 installed on an older machine,
and I could reproduce the issue on amd64 with
"make allmodconfig fs/xfs/xfs_trace.o".

Bisection points to commit e8c07082a810fbb9 ("Kbuild: move to
-std=gnu11").

[1] gcc version 5.5.0 20171010 (Ubuntu 5.5.0-12ubuntu1

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2022-04-04 10:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 22:14 Linux 5.18-rc1 Linus Torvalds
2022-04-04  2:22 ` Guenter Roeck
2022-04-04  3:29   ` Linus Torvalds
2022-04-04  4:23     ` Guenter Roeck
2022-04-04  7:30       ` Ron Economos
2022-04-04 15:32       ` Linus Torvalds
2022-04-04 16:21         ` Greg Kroah-Hartman
2022-04-04 16:45         ` Guenter Roeck
2022-04-04 17:09           ` Linus Torvalds
2022-04-05 21:14           ` Konstantin Ryabitsev
2022-04-04  6:01     ` Jiri Slaby
2022-04-05 12:19   ` Sudip Mukherjee
2022-04-05 13:18     ` Guenter Roeck
2022-04-04  7:47 ` Build regressions/improvements in v5.18-rc1 Geert Uytterhoeven
2022-04-04  8:16   ` Geert Uytterhoeven
2022-04-04  8:16     ` Geert Uytterhoeven
2022-04-04  8:16     ` Geert Uytterhoeven
2022-04-04  9:26     ` Dave Chinner
2022-04-04  9:26       ` Dave Chinner
2022-04-04 10:19       ` Geert Uytterhoeven [this message]
2022-04-04 11:45         ` Arnd Bergmann
2022-04-04 12:31           ` Arnd Bergmann
2022-04-04 22:16           ` Dave Chinner
2022-04-05  6:47             ` Geert Uytterhoeven
2022-04-05  7:08               ` Arnd Bergmann
2022-04-05 21:05                 ` Dave Chinner
2022-04-04 18:39     ` Kalle Valo
2022-04-04 18:39       ` Kalle Valo
2022-04-05  6:46       ` Geert Uytterhoeven
2022-04-05  6:46         ` Geert Uytterhoeven
2022-04-05  6:52         ` Kalle Valo
2022-04-05  6:52           ` Kalle Valo
2022-04-05  6:52           ` Kalle Valo
2022-04-05  6:45     ` Helge Deller
2022-04-05  6:49       ` Geert Uytterhoeven
2022-04-28  7:25         ` Michael Ellerman

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='CAMuHMdWgqdR1o3wT9pjB=w8z=2xaDFv5DJX58-HPHOFRm3Tr8Q@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.