* Speeding up native-comp progress
@ 2020-08-16 8:50 Ethan Edwards
2020-08-16 14:06 ` Andrea Corallo via Emacs development discussions.
0 siblings, 1 reply; 4+ messages in thread
From: Ethan Edwards @ 2020-08-16 8:50 UTC (permalink / raw
To: emacs-devel
Hey all,
I've started compiling my own emacs with my own ./configure flags,
instead of my GNU/Linux Distro's binary. I also have took notice
of the feature/native-comp git branch and compiled it and I've
been using it for about a week and have loved it.
On Reddit there's a post linking to the talk, and one of the comments on
said post is saying that it would likely be Emacs 28 before it was
merged, which is about 2 years away. I would like to know if there's
anything I could do to help speed up that process, for example Bug
Reports, or development, etc.
Thanks.
Ethan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Speeding up native-comp progress
2020-08-16 8:50 Speeding up native-comp progress Ethan Edwards
@ 2020-08-16 14:06 ` Andrea Corallo via Emacs development discussions.
2020-08-16 14:49 ` Ethan Edwards
0 siblings, 1 reply; 4+ messages in thread
From: Andrea Corallo via Emacs development discussions. @ 2020-08-16 14:06 UTC (permalink / raw
To: Ethan Edwards; +Cc: emacs-devel
Ethan Edwards <ethancarteredwards@gmail.com> writes:
> Hey all,
>
> I've started compiling my own emacs with my own ./configure flags,
> instead of my GNU/Linux Distro's binary. I also have took notice
> of the feature/native-comp git branch and compiled it and I've
> been using it for about a week and have loved it.
>
> On Reddit there's a post linking to the talk, and one of the comments on
> said post is saying that it would likely be Emacs 28 before it was
> merged, which is about 2 years away. I would like to know if there's
> anything I could do to help speed up that process, for example Bug
> Reports, or development, etc.
Hi Ethan,
thanks for the mail, is great to ear you enjoy using the branch.
On my side I think precise bug reports are _extremely_ important. For
precise I especially mean providing a clear recipe to reproduce it
starting from scratch. Precise bug reports saves me a lot of time and
greatly help improving the usability of the branch for all users.
Needless to say suggestions and/or patches are greatly appretiated too.
Thanks
Andrea
--
akrl@sdf.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Speeding up native-comp progress
2020-08-16 14:06 ` Andrea Corallo via Emacs development discussions.
@ 2020-08-16 14:49 ` Ethan Edwards
2020-08-16 15:32 ` Andrea Corallo via Emacs development discussions.
0 siblings, 1 reply; 4+ messages in thread
From: Ethan Edwards @ 2020-08-16 14:49 UTC (permalink / raw
To: Andrea Corallo; +Cc: emacs-devel
On Sun, Aug 16, 2020 at 02:06:39PM +0000, Andrea Corallo wrote:
> Hi Ethan,
>
> thanks for the mail, is great to ear you enjoy using the branch.
>
> On my side I think precise bug reports are _extremely_ important. For
> precise I especially mean providing a clear recipe to reproduce it
> starting from scratch. Precise bug reports saves me a lot of time and
> greatly help improving the usability of the branch for all users.
Sure thing, is the bug-gnu-emacs [at] gnu.org the correct mailing list
for these?
>
> Needless to say suggestions and/or patches are greatly appretiated too.
Great, is there a TODO file or anything like that would lead me in a
direction to start? The ./etc/TODO file is exactly the same in both
master and native-comp repo.
Thanks
Ethan
>
> Thanks
>
> Andrea
>
> --
> akrl@sdf.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Speeding up native-comp progress
2020-08-16 14:49 ` Ethan Edwards
@ 2020-08-16 15:32 ` Andrea Corallo via Emacs development discussions.
0 siblings, 0 replies; 4+ messages in thread
From: Andrea Corallo via Emacs development discussions. @ 2020-08-16 15:32 UTC (permalink / raw
To: Ethan Edwards; +Cc: emacs-devel
Ethan Edwards <ethancarteredwards@gmail.com> writes:
> On Sun, Aug 16, 2020 at 02:06:39PM +0000, Andrea Corallo wrote:
>> Hi Ethan,
>>
>> thanks for the mail, is great to ear you enjoy using the branch.
>>
>> On my side I think precise bug reports are _extremely_ important. For
>> precise I especially mean providing a clear recipe to reproduce it
>> starting from scratch. Precise bug reports saves me a lot of time and
>> greatly help improving the usability of the branch for all users.
> Sure thing, is the bug-gnu-emacs [at] gnu.org the correct mailing list
> for these?
Yes M-x report-emacs-bug is the right way to go. We tipically add
[feature/native-comp] in the subject to recognize these, Ex:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42761
>>
>> Needless to say suggestions and/or patches are greatly appretiated too.
> Great, is there a TODO file or anything like that would lead me in a
> direction to start? The ./etc/TODO file is exactly the same in both
> master and native-comp repo.
No unfortunatelly there's no TODO. On my side I'm going to push a
branch reworking the eln placement and compilation trigger mechanism.
This is indirectly open the door for solving once for all the primitive
functions advice issue (probably the cause of some bug still around).
Other than that I've a nuimber of ideas on the performance subject but I
believe the priority should definitely go on tackling and cleaning the
open bugs.
An help in that area can come on trying to reproduce and reduce
analysing reported bug. Often a generic symptom is reported but
investigation is required to find what is the original discrepancy with
the vanilla implementation. This bug is good example of that:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42265
That said any input or suggestion based on the user experience or
improvements (including documentation patches) is very welcome.
Thanks!
Andrea
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-08-16 15:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-08-16 8:50 Speeding up native-comp progress Ethan Edwards
2020-08-16 14:06 ` Andrea Corallo via Emacs development discussions.
2020-08-16 14:49 ` Ethan Edwards
2020-08-16 15:32 ` Andrea Corallo via Emacs development discussions.
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.