Send MinGW-Notify mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."
Please do not reply to this notification; the sender address is unable to
accept incoming e-mail. If you wish to unsubscribe you can do so at
https://lists.osdn.me/mailman/listinfo/mingw-notify.
Today's Topics:
1. [mingw] #41070: Please include libgccjit with MinGW GCC
distribution (MinGW Notification List)
2. [mingw] #41070: Please include libgccjit with MinGW GCC
distribution (MinGW Notification List)
3. [mingw] #41070: Please include libgccjit with MinGW GCC
distribution (MinGW Notification List)
4. [mingw] #41070: Please include libgccjit with MinGW GCC
distribution (MinGW Notification List)
----------------------------------------------------------------------
Message: 1
Date: Sun, 10 Jan 2021 12:40:52 +0000
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41070: Please include libgccjit with
MinGW GCC distribution
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 17:28
Last Update: 2021-01-10 12:40
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-10 12:40 Updated by: keith
Comment:
Reply To eliz
Reply To keith
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.
In the case of libgccjit, to get infrastructure appropriate to MinGW, I did
have to patch the build system. Libtool isn't used, (and wasn't for the
original ELF configuration either. However, that does not prevent us from
adopting the libtool versioning convention; I simply deduced, from the original
soname attributes, that the appropriate current - age value would be zero, and
assigned it manually.
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...
Depends on how you define "compatible". In the MinGW ecosystem, (as it is in
Cygwin's), the version number encoded within the DLL name, (equivalent to
current - age in libtool parlance), represents the oldest current version of
the ABI, with which a particular release of the DLL remains backwardly
compatible. However, there is absolutely no guarantee of forward compatibility;
the most recent release of any particularly named version of a given DLL should
be fully compatible with any application requiring (and possibly working with
an older release of) a similarly named DLL, but older releases of that DLL may
not support a newer application.
The original reference no longer appears to be accessible, but this Wayback
Machine archived reference may help to explain it.
Is libgccjit indeed fully backward compatible, btw?
I don't know for sure, but on the basis of David Malcolm's statement, (and,
AIUI, he is the developer and maintainer of libgccjit), I must assume that it
is.
---------------------------------------------------------------------
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
------------------------------
Message: 2
Date: Sun, 10 Jan 2021 13:03:49 +0000
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41070: Please include libgccjit with
MinGW GCC distribution
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 17:28
Last Update: 2021-01-10 13:03
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-10 13:03 Updated by: keith
Comment:
Reply To eliz
I think statically linking against libintl is a Good Thing,
You are fully entitled to that opinion, but please allow me to disagree...
especially since, as we see, the newer libintl-8.dll is not 100%
compatible, as it causes the program to use libintl's version of setlocale.
If using that entry point could be avoided, then a dynamic dependency on
libintl wouldn't be a problem, I think (or rather hope). Otherwise, it's a
bit of DLL hell, given the same name of the DLL.
Are you saying that you have applications which depend on your older release of
libintl-8.dll, and which will not work with MinGW's latest libintl-8.dll
release? If that is indeed the case, then either your libintl-8.dll, (which I
assume you built yourself), may be incompatible with any MinGW release, or GNU
gettext has introduced an incompatible change, upstream, without making the
necessary adjustment in the libtool versioning attributes; in the latter case,
that should be considered to be an upstream bug, and should be reported as
such. (Do, please, remember that the MinGW/Cygwin DLL versioning conventions
promise only backward compatibility for older applications; there is no
guarantee that an outdated DLL release will remain forward compatible with
newer applications).
---------------------------------------------------------------------
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
------------------------------
Message: 3
Date: Sun, 10 Jan 2021 19:40:12 +0200
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41070: Please include libgccjit with
MinGW GCC distribution
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 19:28
Last Update: 2021-01-10 19:40
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-10 19:40 Updated by: eliz
Comment:
Reply To keith
Reply To eliz
I think statically linking against libintl is a Good Thing,
You are fully entitled to that opinion, but please allow me to disagree...
Can you tell why you disagree?
Are you saying that you have applications which depend on your older
release of libintl-8.dll, and which will not work with MinGW's latest
libintl-8.dll release?
No, that's not what I'm saying. I said "a bit of DLL hell" because I'll have to
cope with 2 different DLLs with the same name.
---------------------------------------------------------------------
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
------------------------------
Message: 4
Date: Sun, 10 Jan 2021 21:56:32 +0000
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41070: Please include libgccjit with
MinGW GCC distribution
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 17:28
Last Update: 2021-01-10 21:56
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-10 21:56 Updated by: keith
Comment:
Reply To eliz
Reply To keith
Reply To eliz
I think statically linking against libintl is a Good Thing,
You are fully entitled to that opinion, but please allow me to
disagree...
Can you tell why you disagree?
We have umpteen different packages — each with a fairly significant build time
— and each individually dependent on libintl. If a bug is identified, in
libintl, and each of those umpteen dependent packages is statically linked with
libintl.a, then when fixing the bug, I have to rebuild every one of those
umpteen dependent packages. If they are linked with libintl-8.dll, then I have
only to fix the bug, and deploy an updated libintl-8.dll, and all of the
umpteen dependent packages inherit the fix, without further effort.
Additionally, although possibly a lesser advantage, but an advantage
nonetheless: linking with shared libraries reduces package size, consequently
reducing disk usage, and upload/download bandwidth.
Are you saying that you have applications which depend on your older
release of libintl-8.dll, and which will not work with MinGW's latest
libintl-8.dll release?
No, that's not what I'm saying. I said "a bit of DLL hell" because I'll
have to cope with 2 different DLLs with the same name.
Why? You should need only the most recent release of libintl-8.dll, (whether
yours or mine), and all of your dependent applications should be happy; no need
for your own (older) version. Besides, if static linking is such a "good
thing", why don't you just link your own applications statically? If you did
this, why was your libintl-8.dll ever needed anyway?
Forgive me, but I simply don't understand your reasoning here.
---------------------------------------------------------------------
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
------------------------------
Subject: Digest Footer
_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify
------------------------------
End of MinGW-Notify Digest, Vol 40, Issue 9
*******************************************
