From: "quic_johmoo at quicinc dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/31017] New: Flex array conversion suppression
Date: Tue, 31 Oct 2023 18:34:13 +0000 [thread overview]
Message-ID: <bug-31017-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31017
Bug ID: 31017
Summary: Flex array conversion suppression
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: quic_johmoo at quicinc dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
In the past, it was common in Linux kernel code to have a "fake flex array" at
the end of a structure. Like this:
struct foo {
int x;
int y;
int end[1];
};
In recent years, with improved compiler support, real flex arrays have been
preferred. It's common to see patches like this:
https://github.com/torvalds/linux/commit/c6f2e6b6eaaf883df482cb94f302acad9b80a2a4
Basically, this takes the struct above, and changes it to:
struct foo {
int x;
int y;
int end[];
};
abidiff flags this change with:
[C] 'struct foo' changed:
type size changed from 96 to 64 (in bits)
1 data member change:
type of 'int end[1]' changed:
type name changed from 'int[1]' to 'int[]'
array type size changed from 32 to 'unknown'
array type subrange 1 changed length from 1 to 'unknown'
It would be good to have a suppression to filter out this kind of change. For
example:
[suppress_type]
type_kind = struct
has_size_change = true
has_strict_flexible_array_data_member_conversion = true
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-10-31 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 18:34 quic_johmoo at quicinc dot com [this message]
2023-11-03 20:58 ` [Bug default/31017] " dodji at redhat dot com
2023-11-04 0:49 ` quic_johmoo at quicinc dot com
2023-11-05 9:43 ` Dodji Seketeli
2023-11-06 17:47 ` John Moon
2023-11-13 13:28 ` Dodji Seketeli
2023-11-05 9:43 ` dodji at seketeli dot org
2023-11-06 17:48 ` quic_johmoo at quicinc dot com
2023-11-13 13:28 ` dodji at seketeli dot org
2023-11-15 4:58 ` quic_johmoo at quicinc dot com
2023-11-15 11:48 ` dodji at redhat dot com
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=bug-31017-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).