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)


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

Message: 1
Date: Tue, 02 Feb 2021 10:58:43 +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-02-02 10:58

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-02-02 10:58 Updated by: keith

Comment:

Reply To davidmalcolm
Looking at the patches themselves:
25-libgccjit-mingw-link-options.patch(3KB)
- Use linker options appropriate for Windows
As far as I can tell, Nicholas made similar changes as part of 
c83027f32d9cca84959c7d6a1e519a0129731501.
Similar in effect, maybe ... streets apart, in implementation detail.  I have 
several reservations about Nicolas' patch, in general, and specific to the 
scope of my 25-libgccjit-mingw-link-options.patch:
Nicolas addresses multiple, logically distinct issues, in a single patch; 
that's a patching strategy with which I, personally, am not comfortable.
Even to the extent that he addresses the issue of linking for MinGW, Nicolas 
has sprayed ifneq blocks around, like the discharge from a blunderbuss; my 
patch consolidates all of the associated logic into a single ifeq...else block.
In naming the DLL shared library, for MinGW, Nicolas has neglected to specify 
an ABI version number, for inclusion within the file name; not only is this 
inconsistent with every other DLL in the GCC universe, it also represents a 
serious deficiency, and is a major contributor to "DLL Hell" for consumers on 
the MS-Windows platform.

---------------------------------------------------------------------
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


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

Message: 2
Date: Tue, 02 Feb 2021 13:47:13 +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-02-02 13:47

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-02-02 13:47 Updated by: keith

Comment:

Expanding on previous comment by keith
Reply To davidmalcolm
Looking at the patches themselves:
25-libgccjit-mingw-link-options.patch(3KB)
- Use linker options appropriate for Windows
As far as I can tell, Nicholas made similar changes as part of 
c83027f32d9cca84959c7d6a1e519a0129731501.

Similar in effect, maybe ... 
Further to my previous comment, in relation to this patch, I notice that 
Nicolas introduced a new installation objective, separating the installation of 
libgccjit header files from the existing jit.install-common objective.  While 
this separation may be advantageous, it is orthogonal to the objective of 
achieving MinGW compatibility; consequently, no such separation is specified in 
my patch series.

---------------------------------------------------------------------
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


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

Message: 3
Date: Tue, 02 Feb 2021 14:51:39 +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-02-02 14:51

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-02-02 14:51 Updated by: keith

Comment:

Reply To davidmalcolm
Looking at the patches themselves:
26-libgccjit-mingw-host-shared.patch(2KB)
- Patch to override --enable-host-shared requirement
As far as I can tell, Nicholas made similar changes as part of 
c83027f32d9cca84959c7d6a1e519a0129731501.
Functionally identical, yes, but I chose not to introduce white-space-only 
changes spanning more than a dozen lines.  I would also respectively suggest 
that Nicolas' "but not if building for Mingw" addition to the comment is 
grossly unsatisfactory ... the code itself tells me that it isn't done for 
MinGW; the comment should explain why.
As an aside, I would also note that both Nicolas' patch, and my 
26-libgccjit-mingw-host-shared.patch, touch both configure.ac, and configure.  
While that is appropriate, for a patch to be applied to a tarball image, in 
which both files must be present, I would question its relevance in a patch 
against an SCM repository; does it not create potential for "thrashing", in the 
content of a generated file, such as configure?  (IMO, generated files, such as 
configure, do not belong in SCM, but I do understand why some developers may 
choose to include them).

---------------------------------------------------------------------
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 41, Issue 3
*******************************************

Reply via email to