From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: Native compiler - passing command line options to C compiler
Date: Wed, 01 Sep 2021 19:45:06 +0300 [thread overview]
Message-ID: <83sfyop7n1.fsf@gnu.org> (raw)
In-Reply-To: <AM9PR09MB49779CD96BCABEB071A8334796CD9@AM9PR09MB4977.eurprd09.prod.outlook.com> (message from Arthur Miller on Wed, 01 Sep 2021 16:23:21 +0200)
> From: Arthur Miller <arthur.miller@live.com>
> Cc: akrl@sdf.org, emacs-devel@gnu.org
> Date: Wed, 01 Sep 2021 16:23:21 +0200
>
> > Almost there: the commit log message should mention the files and
> > functions where you made the changes. Look at the other log messages
> > in git, and you will see the difference (feel free to ask if still
> > unclear).
> >
> > Thanks for working on this.
>
> See if this is ok. I don't know how to get in ` into git message. My bash is
> complaining, but I see in some git log that Lars had quoted some names with `'.
>
> Found also one check for WINDOWS I forgott to remove.
>
> See if this one is ok:
> * lisp/emacs-lisp/comp.el: add user option 'native-comp-compiler-options'
> and rename 'native-comp-driver-options' to 'native-comp-backend-options'
> with changes needed to implement the feature and the rename.
>
> * list/emacs-lisp/bytecomp.el: adapt to the change in comp.el.
>
> * src/comp.c: add support to implement 'native-comp-compiler-options' and
> the rename of driver options to backend options.
This part should look like this:
* lisp/emacs-lisp/comp.el ('native-comp-compiler-options): New option.
(native-comp-driver-options): Rename to 'native-comp-backend-options'.
* list/emacs-lisp/bytecomp.el: All users of 'native-comp-driver-options'
changed.
* src/comp.c (Fcomp_native_backend_options_effective_p): Renamed
from 'Fcomp_native_driver_options_effective_p'; all callers changed.
(Fcomp_native_compiler_options_effective_p): New function.
(add_driver_options): Remove WINDOWSNT condition.
(add_compiler_options): New function.
(Fcomp__compile_ctxt_to_file): Call 'add_compiler_options'.
IOW, you need to list not only the files, but also the functions and
global variables that you change.
This will be much easier if you use "C-x 4 a" or "C-c C-d" (the latter
in the VC log buffer): they will generate the skeleton with file name
and function name for you, so you need just add the description of the
change itself, what's after the colon.
(I can fix the log message for you this time, if you are exhausted ;-)
next prev parent reply other threads:[~2021-09-01 16:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9PR09MB49778CFA83AA6697D09ED01B96CA9@AM9PR09MB4977.eurprd09.prod.outlook.com>
2021-08-30 9:36 ` Native compiler - passing command line options to C compiler Andrea Corallo via Emacs development discussions.
2021-08-30 13:56 ` Arthur Miller
2021-08-30 14:05 ` Andrea Corallo via Emacs development discussions.
2021-08-30 11:42 ` Eli Zaretskii
2021-08-30 12:59 ` Andrea Corallo via Emacs development discussions.
2021-08-30 13:28 ` Eli Zaretskii
2021-08-30 14:28 ` Andrea Corallo via Emacs development discussions.
2021-08-30 15:00 ` Arthur Miller
2021-08-30 15:38 ` Andrea Corallo via Emacs development discussions.
2021-08-31 5:36 ` Arthur Miller
2021-08-31 8:06 ` Andrea Corallo via Emacs development discussions.
2021-08-31 13:01 ` Eli Zaretskii
2021-08-31 22:53 ` Arthur Miller
2021-09-01 11:45 ` Eli Zaretskii
2021-09-01 14:23 ` Arthur Miller
2021-09-01 16:45 ` Eli Zaretskii [this message]
2021-09-01 21:06 ` Arthur Miller
2021-08-30 16:01 ` Eli Zaretskii
2021-08-30 15:50 ` Eli Zaretskii
2021-08-30 14:01 ` Arthur Miller
2021-08-30 14:03 ` Eli Zaretskii
2021-09-01 14:58 ` Alex Bennée
2021-09-01 15:10 ` Perry E. Metzger
2021-09-01 16:04 ` Eli Zaretskii
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=83sfyop7n1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
/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).