From: David Laight <David.Laight@ACULAB.COM>
To: 'Andrew Morton' <akpm@linux-foundation.org>,
Peter Oberparleiter <oberpar@linux.ibm.com>
Cc: "Martin Liška" <mliska@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] gcov: support GCC 12.1 and newer compilers
Date: Mon, 17 Oct 2022 11:38:24 +0000 [thread overview]
Message-ID: <9b724e2af2d048c3a7f7f20ae0942ab6@AcuMS.aculab.com> (raw)
In-Reply-To: <20221016174033.d33a998b4c91b7d18b3dc310@linux-foundation.org>
From: Andrew Morton
> Sent: 17 October 2022 01:41
..
> The changelog doesn't tell us what the user-visible effects of this are
> (please, it should do so), but it sounds to me like those effects are
> "gcov is utterly busted".
>
> So I'll add a cc:stable to this, so that people can use new gcc
> versions to build older kernels.
I can't help wondering what happens if you link a binary
compiled with an old gcc with one build with a new gcc?
This could easily happen with out of tree loadable modules.
Or just linking an old .a file into a userspace binary.
Now maybe the gcov data isn't used (I've not looked up what
it is for) but is sounds like something whose format should
be set in stone?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-10-17 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 7:40 Martin Liška
2022-10-14 9:30 ` Peter Oberparleiter
2022-10-17 0:40 ` Andrew Morton
2022-10-17 8:02 ` Martin Liška
2022-10-17 11:38 ` David Laight [this message]
2022-10-17 12:23 ` Martin Liška
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=9b724e2af2d048c3a7f7f20ae0942ab6@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mliska@suse.cz \
--cc=oberpar@linux.ibm.com \
/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
all inboxes | Powered by JetHome®