From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Merging feature/android Date: Sat, 04 Mar 2023 14:49:38 +0200 Message-ID: <83r0u4adgd.fsf@gnu.org> References: <87edq7ztks.fsf.ref@yahoo.com> <87edq7ztks.fsf@yahoo.com> <83pm9reccn.fsf@gnu.org> <87v8jjxxo9.fsf@yahoo.com> <835ybje2u5.fsf@gnu.org> <87fsanxoah.fsf@yahoo.com> <83zg8vckx5.fsf@gnu.org> <87bklay7wg.fsf@yahoo.com> <83ilficn4k.fsf@gnu.org> <87zg8uw9b9.fsf@yahoo.com> <837cvycjse.fsf@gnu.org> <87ttz2w4c3.fsf@yahoo.com> <83356mcbxw.fsf@gnu.org> <87pm9qvu9w.fsf@yahoo.com> <83y1odc37g.fsf@gnu.org> <87cz5pwf9c.fsf@yahoo.com> <83edq5asb3.fsf@gnu.org> <875ybhvt4w.fsf@yahoo.com> <83356kbxnh.fsf@gnu.org> <87lekcvho4.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38061"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 04 13:50:42 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pYRLW-0009dO-FZ for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Mar 2023 13:50:42 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pYRKj-0005Aj-6K; Sat, 04 Mar 2023 07:49:53 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pYRKh-0005AS-Vc for emacs-devel@gnu.org; Sat, 04 Mar 2023 07:49:51 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pYRKg-0004qG-CL; Sat, 04 Mar 2023 07:49:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=BqitbPMFJLWRU9YxeJZZADoC4Lyp+JVQlXn4U9Pq13E=; b=m09+zOHQHBQi t9tJgp8fdBhRLIe4JFhblDF4WMVk+eps7z1YxY3SLbSWNNC3o2kqpSDlEByf/Ofzzgdftci2xFEYt k+RHaatbo9gHhKCM/wegu1xtVVF8ylPUZonHMZfKQLhVFAq1hRx/qubw38v7Y69cEFgdllfLFvC7L R0WxGwgMlTJKlQykWtu0oc6GviMTQ7FrL27r5bJv+ZrffsKuAIpuRIopMWnvBJlQIYvS8yQN7made o7o6t7c+PZ4PGSjZIdzjkfnfgmE9QFz0gT1PBd5AGfZ1uJn2bGDeA12BBQNmZJ33FT/OBvj3aKPiW ekPvRRJLh5UTIggbJ+4NTg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pYRKf-000715-JC; Sat, 04 Mar 2023 07:49:49 -0500 In-Reply-To: <87lekcvho4.fsf@yahoo.com> (message from Po Lu on Sat, 04 Mar 2023 20:12:59 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303945 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu > Date: Sat, 04 Mar 2023 20:12:59 +0800 > > Eli Zaretskii writes: > > > What are those "non-GCC and non-Clang compilers" that are prone to > > this problem? > > tcc, for instance. Or the various compilers found on Unix systems. And Emacs can be, and is actually, built with them? > > I'm okay with writing tests for this, but can be arrange for those > > tests to be run only in the Android build? Once again, I'd prefer not > > to make non-trivial changes in our configury with a clear test case, > > and we don't have any such case that doesn't involve the Android > > build, AFAIU. > > We should not assume that all the world is any specific compiler, be it > GCC or Clang. We don't. Function attributes are widely used feature nowadays. > Especially not in a configure script, whose job is to make sure > Emacs can adapt itself to any reasonable Unix system, including ones > that may show up in the future, such as a tcc-based GNU/Linux > system. Our configury is complicated enough for us to avoid solving any theoretical problems by further complicating it. I'm mainly bothered by any possible effect this could have on users who configure Emacs, and would like to avoid any unnecessary risks.