public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100613] libgccjit should produce dylib on macOS
Date: Thu, 05 Aug 2021 12:26:39 +0000	[thread overview]
Message-ID: <bug-100613-4-joXplCHyAB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100613-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100613

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|dmalcolm at gcc dot gnu.org        |iains at gcc dot gnu.org
   Last reconfirmed|                            |2021-08-05
             Status|UNCONFIRMED                 |NEW
   Target Milestone|---                         |11.3
     Ever confirmed|0                           |1

--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> ---
I have a preference for setting the correct library name when it is created,
and for setting the library versioning information in the 'usual' Darwin way.

The reason being that I have patches in flight for using "@rpath/....." for the
library names to fix the issues we have with testing on platforms with SIP
enabled (post 10.11).

Patches are under test.

NOTE there are issues with testing too - namely that the testsuite code is
currently making assumptions about support for --export-dynamic (it should
conditionally use -rdynamic IMO) and also that it assumes dejagnu.h is visible
in the default compiler lookup paths (it isn't on Darwin)... then we reach the
obstacle that the dejagnu.h from at least 1.6.2 has an unused variable in C
compilations + the wait function declaration clashes with the system's decl for
'wait'.

When all these things are fixed, we have two more issues that I've not been
able to address yet - namely that we get bad code-gen when "-g" is on the
command line, and that it seems that sometimes we get hanging tests that are
not killed by the testsuite machinery - so that the whole "make check" hangs.

At least I plan to address the issues for which the solution is clear - for the
last two things I think that more understanding of the processes used by the
Jit will be needed.

  parent reply	other threads:[~2021-08-05 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 13:07 [Bug jit/100613] New: " wyuenho at gmail dot com
2021-05-17 12:30 ` [Bug jit/100613] " egallager at gcc dot gnu.org
2021-08-05 12:26 ` iains at gcc dot gnu.org [this message]
2021-08-18 18:52 ` cvs-commit at gcc dot gnu.org
2022-04-14  5:22 ` cvs-commit at gcc dot gnu.org
2022-04-21  7:49 ` rguenth at gcc dot gnu.org
2022-06-09 19:22 ` cvs-commit at gcc dot gnu.org
2022-06-09 19:30 ` iains at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100613-4-joXplCHyAB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).