unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45817@debbugs.gnu.org, kirill@korins.ky
Subject: bug#45817: 28.0.50; Native fails
Date: Thu, 14 Jan 2021 16:04:54 +0200	[thread overview]
Message-ID: <83sg73bomx.fsf@gnu.org> (raw)
In-Reply-To: <xjf5z3z50cj.fsf@sdf.org> (message from Andrea Corallo on Thu, 14 Jan 2021 09:33:48 +0000)

> From: Andrea Corallo <akrl@sdf.org>
> Cc: "Kirill A. Korinsky" <kirill@korins.ky>, 45817@debbugs.gnu.org
> Date: Thu, 14 Jan 2021 09:33:48 +0000
> 
> > Is this specific to macOS?
> >
> > In any case, if it's known that specific versions of GCC cause
> > problems on specific platforms, we should reject those versions (for
> > the libgccjit usage purposes) in configure, I think.
> 
> We do, not based on the version but (even better I think) we run a
> functional test at configure time.  The test use libgccjit to produce a
> shared, then this is loaded and used to ensure all the complete
> mechanism is functional.

Yes, but such tests can only verify that the basics work, whereas the
OP seemed to indicate that it generally works, but fails in some
subtle situation.  If libgccjit you are testing at configure time only
"mostly" works, you will be unable to detect that with simple tests.
For such subtly broken versions of libgccjit, we have no practical
means but looking at their version.

> I think in this specific case somenthing happend (maybe OS upgrade?) as
> when Emacs was compiled libgccjit clearly was working.

If that is the case, then there's no problem we need to solve here.





  reply	other threads:[~2021-01-14 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 15:04 bug#45817: 28.0.50; Native fails Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <handler.45817.B.161046478816838.ack@debbugs.gnu.org>
2021-01-12 18:10   ` bug#45817: Acknowledgement (28.0.50; Native fails) Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 18:44     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 19:35       ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 20:09         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 19:38 ` bug#45817: 28.0.50; Native fails Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 20:05   ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 20:25     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 20:44       ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14  2:19         ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14  3:32           ` Eli Zaretskii
2021-01-14  9:33             ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 14:04               ` Eli Zaretskii [this message]
2021-01-14 14:31                 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 10:51             ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14  9:34           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83sg73bomx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45817@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=kirill@korins.ky \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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