Re: Native Compilation And External Packages

["T.V Raman" <raman@google.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1649 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

I'll write up these as bug reports, now that I have a somewhat better
sense as to what it is I am reporting.

At present, there appears to be a lot of "magic" in the bits around jit
compilation, when emacs decides to generate a new .eln file etc, which
makes it hard to discern a bug from a feature and consequently, phrasing
a sensible question is hard as these threads have demonstrated.

Also, I suspect that filing a bug report would have caused folks looking
at it to "file a simple   repro case", and that is something I
definitely wont be able to do given that I'm chasing this down with a
fairly large package as the use-case.



> T.V Raman [2021-05-29 10:14:43] wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>> The warnings are inconsistent as in:
>
> Please, please, pretty please write this in a bug report.
>
> Or better yet, two bug reports: one for the case where you replace
> `batch-byte-compile` with `batch-native-compile`, and another for the
> case where native compilation takes place lazily.
>
> The "extra warnings" during lazy native compilation is a known problem,
> but one we need to address, so making a bug report about it will
> be helpful.
>
> The problems you mentioned when replacing `batch-byte-compile` with
> `batch-native-compile` OTOH are not known, AFAIK, so we really need
> a clear bug report with details of what you did, what that got you, and
> why you think it's wrong about that.
>
>
>         Stefan
>
>

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8