From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: stable@vger.kernel.org
Subject: Re: 5.15.x: randomize_layout_plugin.c: 'last_stmt' was not declared in this scope?
Date: Tue, 16 Jul 2024 16:08:44 +0200 [thread overview]
Message-ID: <2024071653-glider-plated-0a61@gregkh> (raw)
In-Reply-To: <ZpO2yOXdylWmyaaj@localhost.localdomain>
On Sun, Jul 14, 2024 at 01:30:16PM +0200, Thomas Meyer wrote:
> Good day,
>
> I wanted to upgrade my kernel to the latest 5.15.162 but it seems to fail with
> this error message after upgrading to fedora 40, any ideas what could be the
> problem?
>
> $ make
> HOSTCXX scripts/gcc-plugins/randomize_layout_plugin.so
> scripts/gcc-plugins/randomize_layout_plugin.c: In function 'bool dominated_by_is_err(const_tree, basic_block)':
> scripts/gcc-plugins/randomize_layout_plugin.c:693:20: error: 'last_stmt' was not declared in this scope; did you mean 'call_stmt'?
> 693 | dom_stmt = last_stmt(dom);
> | ^~~~~~~~~
> | call_stmt
> make[2]: *** [scripts/gcc-plugins/Makefile:48: scripts/gcc-plugins/randomize_layout_plugin.so] Error 1
> make[1]: *** [scripts/Makefile.build:552: scripts/gcc-plugins] Error 2
> make: *** [Makefile:1246: scripts] Error 2
>
> Maybe a problem with gcc 14?
Maybe, has any previous 5.15.y kernel worked?
> My current kernel was compiled with gcc 13:
> [ 0.000000] [ T0] Linux version 5.15.160 (thomas2@localhost.localdomain) (gcc (GCC) 13.3.1 20240522 (Red Hat 13.3.1-1), GNU ld version 2.40-14.fc39) #15 PREEMPT Sat Jun 1 16:54:27 CEST 2024
If you build 5.15.160 with gcc 14 does it also fail? Doing a 'git
bisect if it does not would be great to track down the offending commit.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-16 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 11:30 5.15.x: randomize_layout_plugin.c: 'last_stmt' was not declared in this scope? Thomas Meyer
2024-07-16 14:08 ` Greg KH [this message]
2024-07-20 19:54 ` Thomas Meyer
2024-07-22 12:00 ` Greg KH
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=2024071653-glider-plated-0a61@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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