Fork#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 19:28
Last Update: 2021-01-09 10:22
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 10:22 Updated by: eliz
Comment:
Reply To keith
Reply To eliz
Btw, judging by the Info manual that comes with libgccjit, a more
appropriate name for the DLL would be libgccjit-10.dll, since it
implements LIBGCCJIT_ABI_10 (and the next versions of GCC advance the
ABI by several more notches). MinGW64 also calls it libgccjit-0.dll, so
we could adopt the same name, regardless. But then we will need to
invent ABI numbers out of thin air for future releases, which might be
sub-optimal.
Our DLL version numbering scheme, like that also used by Cygwin, is based
on the libtool interface version numbering conventions; like Cygwin, we
compute the number, included within the DLL file name, as the libtool
current version number minus the libtool age. In this case, current would
appear to be 10, but, as David has indicated, ABI 10 is backwardly
compatible with ABI 0, and every version between. Thus, age would also be
10, and the appropriate current - age result is, indeed, 0.
I'm aware of the numbering scheme, I just wasn't sure that libtool was involved
in the build and applied the scheme. From your description I deduced, perhaps
incorrectly, that building libgccjit for MinGW was not yet supported, and that
led me to the conclusion that perhaps the 0 part was some kind of default, not
a number correctly calculated from the ABI data.
It is also a certain surprise for me to read that adding entry points is still
considered to be a "compatible" ABI. I always thought that if the DLL name
remains the same, then any program linked against any version with that name
will be able to run with any other version of that DLL that has the same name.
I guess there's something new to learn every day...
Is libgccjit indeed fully backward compatible, btw?
---------------------------------------------------------------------
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