all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	68851@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#68851: 30.0.50; Native comp: Optimization failure for org-element-property-raw: Handler: org-element-property-raw--inliner
Date: Thu, 08 Feb 2024 23:06:52 +0000	[thread overview]
Message-ID: <877cjev9mb.fsf@localhost> (raw)
In-Reply-To: <yp1mssad1rr.fsf@fencepost.gnu.org>

Andrea Corallo <acorallo@gnu.org> writes:

>> cd org-mode/lisp
>> emacs  -Q -batch --eval '(add-to-list '"'"'load-path ".")' --eval '(batch-native-compile)' org-element-ast.el
>
> Negative, I've already the invocation for the native compilation, what I
> want is the one for byte compilation.
>
> Reason for that is that my crystal ball suggests compilers are invoked
> in different ways.  Actually
>
> emacs  -Q -batch --eval '(add-to-list '"'"'load-path ".")' --eval '(batch-byte-compile)' org-element-ast.el
>
> gives here the same exact error the native compiler gives.

I confirm.

> That BTW is in disagreement with:
>
>>> Ihor have you tried compiling the compilation unit from command line
>>> (using batch-byte-compile or batch-native-compile)?  If some dependency
>>> is broken this should highlight it.
>>
>> batch-byte-compile does not emit any warnings.
>> batch-native-compile emits the same warning:

Hmm. I think what I tried was a bit different. I did make compile, which
is using batch-byte-recompile-directory:

emacs  -Q -batch --eval '(add-to-list '"'"'load-path ".")' --eval '(batch-byte-recompile-directory 0)'

> So I suspect that (if this is really a bug) is not native compiler
> related, but I need the second invocation to confirm.

Looks like it is really not native compiler related.
Still, I am puzzled what is going wrong there. The error is

Warning: Optimization failure for org-element-property-raw: Handler: org-element-property-raw--inliner
(void-function org-element--property-idx)

but both org-element--property-idx and org-element-property-raw are
inline functions defined in the same file.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2024-02-08 23:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 13:50 bug#68851: 30.0.50; Native comp: Optimization failure for org-element-property-raw: Handler: org-element-property-raw--inliner Ihor Radchenko
2024-01-31 14:20 ` Eli Zaretskii
2024-02-02  9:00   ` Andrea Corallo
2024-02-02 13:35     ` Ihor Radchenko
2024-02-05 15:10       ` Andrea Corallo
2024-02-08 18:49       ` Andrea Corallo
2024-02-08 19:21         ` Ihor Radchenko
2024-02-08 21:43           ` Andrea Corallo
2024-02-08 21:51             ` Ihor Radchenko
2024-02-08 21:57               ` Andrea Corallo
2024-02-08 22:13                 ` Ihor Radchenko
2024-02-08 22:33                   ` Andrea Corallo
2024-02-08 23:06                     ` Ihor Radchenko [this message]
2024-02-08 23:30                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 23:42                         ` Ihor Radchenko
2024-02-09  0:47                           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 12:02                             ` Ihor Radchenko
2024-02-09 12:42                               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 16:21                                 ` Ihor Radchenko
2024-02-09 16:19                             ` Ihor Radchenko
2024-02-09 11:41                       ` Andrea Corallo
2024-01-31 19:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-31 19:47   ` Ihor Radchenko

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=877cjev9mb.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=68851@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.