From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 46983@debbugs.gnu.org
Cc: eliz@gnu.org
Subject: bug#46983: 28.0.50; [feature/native] Allow .el files to specify non-default values for native-compilation options
Date: Sun, 07 Mar 2021 19:35:01 +0000 [thread overview]
Message-ID: <xjfa6re21wa.fsf@sdf.org> (raw)
In-Reply-To: <xjf5z23314h.fsf@sdf.org> (Andrea Corallo via's message of "Sun, 07 Mar 2021 06:54:06 +0000")
Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> This is a feature request. Since there are various stability and
>> reliability issues with libgccjit, some Emacs Lisp files may need to
>> specify non-default values for some native-compilation options, such as
>> 'comp-speed' or 'comp-native-driver-options'.
>
> Hi Eli,
>
> if the interface we'd like to expose is the through file-local variables
> then this should work already for `comp-speed' and `comp-debug',
> I'extend it for `comp-native-driver-options'.
Okay dbdc44db15 should allow for `comp-native-driver-options' as
file-local to be captured correctly.
But...
I've only added 'gcc_jit_context_add_driver_option' to GCC 9 so we have
to decide what to do when this is not available on older GCC.
Till today we raised an error as the use of `comp-native-driver-options'
was a deliberate user choice and it's effectiveness was testable with
`comp-native-driver-options-effective-p', but if this becomes part of
source code we should probably transition to a warining? WDYT?
Thanks
Andrea
next prev parent reply other threads:[~2021-03-07 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 5:43 bug#46983: 28.0.50; [feature/native] Allow .el files to specify non-default values for native-compilation options Eli Zaretskii
2021-03-07 6:54 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-07 7:23 ` Eli Zaretskii
2021-03-12 12:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 12:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-12 16:08 ` Eli Zaretskii
2021-03-07 19:35 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-07 20:18 ` Eli Zaretskii
2021-03-07 20:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-07 21:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfa6re21wa.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=46983@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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).