From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by sourceware.org (Postfix) with ESMTPS id 5793D3858427 for ; Mon, 9 May 2022 09:22:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5793D3858427 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f51.google.com with SMTP id c11so18502480wrn.8 for ; Mon, 09 May 2022 02:22:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=oNhi0nQox7w68MniTeWZp2iQEVKekx+zmHmdEJ3Y5Ls=; b=2o8qezfBgeW18pIhoRHkoUkQ8+V/r3M7SOH+2YdlwYtHdMlnbyR/CrCewYfUmXm5Hl NiJ09M3tozhkqlbkoGtaTxmrV7eFUCnxKLy0CoYxAN47SWc//owKKWFMxBdaJ8N+Fxc/ TwqGx7EzC62gHiABVVZ1Apd8QrcZ0L+mSrGJRO5usQOkgkP2oVx9fYEuTXEoIvmR8nec oBSNDWSEdiz/Yy+rCz+aR+XikORadz5IsKp0IU0P7z8aArFw1EQa8y8Ock3dluiQOrUZ UniByE/h1laMsNboGqZW5OObGaN1nmB4f/DlvH4jw0K4Ks+Kx3I2c7YmwnQ2b2UgeHmN cIyA== X-Gm-Message-State: AOAM532vm49W/wJqlGSdvu5jHPIACyjNQDAjME9rbvXbeviavw8SOTtu 5MAghrfgmHEtX3TgzCdYQNA2i70R9C4= X-Google-Smtp-Source: ABdhPJzY8OGJvr8dH79JfbRXzdR5nVquv1DsHi1NeohjZftU3Jfucgwfz8APCveQXKmPivutCmT/2A== X-Received: by 2002:a5d:4dcc:0:b0:20a:ddaa:1c30 with SMTP id f12-20020a5d4dcc000000b0020addaa1c30mr12323124wru.419.1652088161933; Mon, 09 May 2022 02:22:41 -0700 (PDT) Received: from ?IPV6:2001:8a0:f924:2600:209d:85e2:409e:8726? ([2001:8a0:f924:2600:209d:85e2:409e:8726]) by smtp.gmail.com with ESMTPSA id r10-20020adfa14a000000b0020cd0762f37sm814144wrr.107.2022.05.09.02.22.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 May 2022 02:22:40 -0700 (PDT) Message-ID: <70918576-c535-0218-720f-24ac44af4091@palves.net> Date: Mon, 9 May 2022 10:22:39 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Do we support Not ANSI C compiler? Content-Language: en-US To: =?UTF-8?Q?Martin_Li=c5=a1ka?= , Binutils References: <99b5380e-8072-dd67-497d-94f72eee43c3@suse.cz> From: Pedro Alves In-Reply-To: <99b5380e-8072-dd67-497d-94f72eee43c3@suse.cz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2022 09:22:44 -0000 On 2022-05-09 09:49, Martin Liška wrote: > Hi. > > I noticed ./include/ansidecl.h contains not ANSI C path: > > #else /* Not ANSI C. */ > > #define PTR char * > > /* some systems define these in header files for non-ansi mode */ > #undef const > #undef volatile > #undef signed > #undef inline > #define const > #define volatile > #define signed > #define inline > > #endif /* ANSI C. */ > > And my question is if we really support such compilers or can we remove the hunk? Given: - GCC requires C++11 nowadays, - GDB requires C++11 nowadays, - Binutils requires C99 nowadays (for over a year), I'd think that no, we no longer support such compilers and we can remove the hunk.