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)
----------------------------------------------------------------------
Message: 1
Date: Wed, 27 Jan 2021 19:42: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-27 19:42
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-27 19:42 Updated by: keith
Comment:
Reply To davidmalcolm
I've now looked through the patches themselves, and suddenly realized that they
conflict in places with
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=c83027f32d9cca84959c7d6a1e519a0129731501
by Nicolas Bértolo which is on "master" for gcc 11, but not on the branches for
older releases. It looks like this might do much of what your patches do.
Quite possibly. As Eli has already pointed out, Nicolas is focussed on work
for MINGW64 — actually the trademark-infringing mingw-w64 project — whereas my
efforts are on behalf of the legitimate owner of the MinGW trademark. I guess
it's inevitable that we would come up with some very similar changes. In any
case, I'm not at all enthusiastic about the way in which Nicolas has bundled
everything into just one patch; I much prefer a coherent series of granular
patches, (which I can manage with Mercurial Queues), so that I can more readily
adapt to variations between releases, (and to conflicts with other
contributors' patches).
Is this patch in the code that you're working with?
No, I don't think so.
What GCC version are you using?
As I mentioned, in an earlier comment, the last GCC release I've published for
MinGW is GCC-9.2.0; I've simply been tweaking my existing build tree for that,
to explore the feasibility of incorporating libgccjit support, before I move on
to GCC-10. (I tend to match my build cycles, as my available time permits, to
the native compiler version on my Manjaro-Linux build machine; this is
currently GCC-10.2).
Should this be backported; if so, which version?
I already have a significant collection of local patches — 28 currently, with 3
no longer required — which I apply for MinGW releases; I'm quite happy to
continue with this publication strategy, so, while backporting may be useful,
it's by no means imperative. I will not be looking at anything earlier than
GCC-9.2.0, as a MinGW libgccjit candidate.
I'm sorry for not noticing this earlier in this discussion (in my defence it
was back in May, and 2020 has been a difficult year).
Don't we all know it :-)
That said, your patches do have additional changes that appear to be necessary
(in particular the mutex one). I wonder why Nicholas got it working, but you
needed additional patches. Maybe he merely fixed the build, not the actually
execution?
I can't speak for anything emanating from the mingw-w64 folks — they are a law
on to themselves. Perhaps Nicolas was happy to introduce a dependency on a
third-party (their own?) implementation of POSIX threads for Windows. I could
have done likewise, but I much prefer the native solution.
Do you have a copyright assignment in place with the FSF?
I do, in respect of my contributions to the GNU troff (groff) project, but not
specific to GCC.
---------------------------------------------------------------------
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:
ease 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 12
********************************************
