From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <acorallo@gnu.org>,
68851@debbugs.gnu.org
Subject: bug#68851: 30.0.50; Native comp: Optimization failure for org-element-property-raw: Handler: org-element-property-raw--inliner
Date: Fri, 09 Feb 2024 12:02:56 +0000 [thread overview]
Message-ID: <87plx5etfz.fsf@localhost> (raw)
In-Reply-To: <jwv8r3umpq3.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> `org-element--property-idx` is defined in that same file, indeed, but
>>> contrary to `defmacro`, `define-inline` does not make the function
>>> usable during that same file's compilation.
>> This is surprising. I would not mind compiler indicating this fact in
>> less cryptic way or, better, making `define-inline' usable during file's
>> compilation.
>
> The same error would be signaled if `org-element--property-idx` were
> defined with `defun`, and `define-inline` is another way to define
> a function, so I thought it would make sense to make them
> behave similarly.
I see the logic.
Although, I am very surprised that `batch-byte-recompile-directory' does
not trigger the error. So, something is off somewhere in the
compilation. If not in `batch-byte-compile' then in
`batch-byte-recompile-directory'.
--
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>
next prev parent reply other threads:[~2024-02-09 12:02 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
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 [this message]
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=87plx5etfz.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.