From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Brahmajit <brahmajit.xyz@gmail.com>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c
Date: Tue, 1 Oct 2024 16:28:25 +0300 [thread overview]
Message-ID: <Zvv4-bm07rb9rfK_@intel.com> (raw)
In-Reply-To: <sstecaeritl7w2eu5swqmshi5vbvjpeaufwilqdg2jhtnsnpys@iggjwl7wmibo>
On Tue, Oct 01, 2024 at 11:48:56AM +0530, Brahmajit wrote:
> On 01.10.2024 11:45, Brahmajit wrote:
> > While building the latest stable release with GCC 15 I'm getting an
> > build error with (I'm guessing) the drm module. This is probably due to
> > combination of GCC 15's introduction of a new warning
> > -Wunterminated-string-initialization, -Werror and -Wextra
> >
> > In the drivers/gpu/drm/display/drm_dp_dual_mode_helper.c file there is a
> > code section on 163
> >
> > static const char dp_dual_mode_hdmi_id[DP_DUAL_MODE_HDMI_ID_LEN] =
> > "DP-HDMI ADAPTOR\x04";
> >
> > Its from the is_hdmi_adaptor() function.
> > I read a little about C strings and it seems like we are assigning more
> > than 16 characters to the array dp_dual_mode_hdmi_id, and
> > DP_DUAL_MODE_HDMI_ID_LEN is defined as 16.
> >
> > I'm guessing this has something to do with how termination happens in
> > char array vs char* and/or null termination
>
> Some references I found:
> - https://lore.kernel.org/linux-btrfs/5mnphkdvheudccjtiatrbjbkqtw54s2wkpeqevj3rqthdqlwyw@sjvn4wn52qki/
> - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185
Looks like gcc is warning about perfectly legal code
(as far as the C standard goes).
But we could work around by adding room for the '\0' and
s/sizeof(...)/DP_DUAL_MODE_HDMI_ID_LEN/ in the memcmp().
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-10-01 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 6:15 Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c Brahmajit
2024-10-01 6:18 ` Brahmajit
2024-10-01 13:28 ` Ville Syrjälä [this message]
2024-10-01 13:42 ` Brahmajit
2024-10-01 13:48 ` Brahmajit
2024-10-01 14:02 ` Ville Syrjälä
2024-10-01 14:06 ` Brahmajit
2024-10-01 14:12 ` Ville Syrjälä
2024-10-01 14:14 ` Brahmajit
2024-10-01 14:34 ` Brahmajit
2024-10-01 14:36 ` [PATCH 1/1] drm/display: Fix building with GCC 15 Brahmajit Das
2024-10-01 14:10 ` Build failure with GCC 15 in drivers/gpu/drm/display/drm_dp_dual_mode_helper.c Ville Syrjälä
-- strict thread matches above, loose matches on Subject: below --
2024-10-01 12:53 Brahmajit
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=Zvv4-bm07rb9rfK_@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=brahmajit.xyz@gmail.com \
--cc=linux-newbie@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.