[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Native compilation on as default?
From: |
Andrea Corallo |
Subject: |
Re: Native compilation on as default? |
Date: |
Mon, 20 Nov 2023 04:41:05 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>> Date: Wed, 25 Oct 2023 16:50:17 -0400
>>
>> So I think we could have a new mode, still controlled by
>> native-comp-async-report-warnings-errors, that filters out all the
>> uninteresting warnings (that the programmer already got during byte
>> compilation) but still report this important one.
>>
>> So even if the package developer doesn't use native compilation it can
>> get the bug report for the issue.
>>
>> I suspect this might be a good compromise/solution.
>>
>> WDYT?
>
> Sounds like a plan to me, thanks.
While adding this entry in TODO came to my mind this thread.
What is the the outcome? Are we fine in activating native comp by
default when libgccjit is available?
Thanks
Andrea
- Re: Native compilation on as default?,
Andrea Corallo <=