[MinGW-Notify] [mingw] #41070: Please include libgccjit with MinGW GCC distribution

Back to archive index
MinGW Notification List mingw****@lists*****
Sat Jan 9 01:54:21 JST 2021


#41070: Please include libgccjit with MinGW GCC distribution

  Open Date: 2020-12-24 02:28
Last Update: 2021-01-09 01:54

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/41070
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41070

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2021-01-09 01:54 Updated by: davidmalcolm

Comment:

Sorry about the confusion. The information I posted is more aimed at packagers
and maintainers than end-users.

For example, on my RPM-based system, I can run:

$ rpm -q --provides libgccjit
libgccjit = 10.2.1-1.fc32
libgccjit(x86-64) = 10.2.1-1.fc32
libgccjit.so.0()(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_0)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_1)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_10)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_11)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_12)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_13)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_2)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_3)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_4)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_5)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_6)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_7)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_8)(64bit)
libgccjit.so.0(LIBGCCJIT_ABI_9)(64bit)

where the versions get detected by rpmbuild and "baked into" the package
metadata. Similarly, packages that use libgccjit can record exactly which ABI
they were built again in their package metadata, ensuring that RPM can enforce
compatibility, whilst also allowing new API/ABI entrypoints to be added without
bumping the SONAME, which would require everything to be recompiled.

This relies on the dynamic loader being able to express this information and
enforce it, which is the case for glibc's ld.so.

It sounds like the windows dynamic linker either doesn't have these
capabilities, or has different ones, and that I've assumed too much.

Does the windows dynamic linker have any such abilities, or do we simply need
to express the ABI version in the dll name, or somesuch?

Hope this makes sense



---------------------------------------------------------------------
Ticket Status:

      Reporter: eliz
         Owner: keith
          Type: Feature Request
        Status: Open [Owner assigned]
      Priority: 5 - Medium
     MileStone: (None)
     Component: GCC
      Severity: 5 - Medium
    Resolution: None
---------------------------------------------------------------------

Ticket details:

Please add libgccjit to the binaries included in the MinGW GCC distributions.
This is required to be able to build projects that use libgccjit for JIT
compilation of code. One example of this is "gccemacs", a branch of GNU Emacs
development (soon to land on the master branch of Emacs) that compiles Emacs
Lisp programs into native x86 code for faster runtime performance.

Thank you.



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/41070
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41070



More information about the MinGW-Notify mailing list
Back to archive index