Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Dec 2022 22:46:39 +0000
From:      bugzilla-noreply@freebsd.org
To:        mono@FreeBSD.org
Subject:   [Bug 268321] lang/mono: fix build with clang 15 (on i386)
Message-ID:  <bug-268321-23699@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268321

            Bug ID: 268321
           Summary: lang/mono: fix build with clang 15 (on i386)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: mono@FreeBSD.org
          Reporter: dim@FreeBSD.org
             Flags: maintainer-feedback?(mono@FreeBSD.org)
          Assignee: mono@FreeBSD.org

During an exp-run for llvm 15 (see bug 265425), it turned out that lang/mono
failed to build with clang 15, on i386:

  mini-runtime.c:806:24: error: incompatible pointer to integer conversion
assigning to 'guint32' (aka 'unsigned int') from 'MonoLMF *' (aka 'struct
MonoLMF *') [-Wint-conversion]
          ext->lmf.previous_lmf =3D *lmf_addr;
                                ^ ~~~~~~~~~
  mini-runtime.c:808:24: error: incompatible pointer to integer conversion
assigning to 'guint32' (aka 'unsigned int') from 'gpointer' (aka 'void *')
[-Wint-conversion]
          ext->lmf.previous_lmf =3D (gpointer)(((gssize)ext->lmf.previous_l=
mf) |
2);
                                ^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As noted, this is because on i386 the previous_lmf field is declared as
guint32, while other architectures use gpointer.

Upstream changed the field to gpointer in
<https://github.com/mono/mono/pull/8308/commits/1c43a8476b5>, which got mer=
ged
into main in <https://github.com/mono/mono/commit/384c4a4e2ea>.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268321-23699>