From nobody Wed May 31 13:11:15 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWV5Z0sb9z4YgWY for ; Wed, 31 May 2023 13:11:30 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from mail.yourbox.net (mail.yourbox.net [IPv6:2001:41d0:1:767d::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.yourbox.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWV5Y07Qxz45Df; Wed, 31 May 2023 13:11:28 +0000 (UTC) (envelope-from fbl@aoek.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aoek.com header.s=mailbox header.b=Uql0fQUH; spf=pass (mx1.freebsd.org: domain of fbl@aoek.com designates 2001:41d0:1:767d::1 as permitted sender) smtp.mailfrom=fbl@aoek.com; dmarc=pass (policy=reject) header.from=aoek.com Received: from mail.yourbox.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail.yourbox.net (8.17.1/8.17.1) with ESMTP id 34VDBKgT090588; Wed, 31 May 2023 15:11:20 +0200 (CEST) (envelope-from fbl@aoek.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aoek.com; s=mailbox; t=1685538680; bh=dp+QWor5my5KjxQWH9OdbIjhcp082Er68zyA7hfgPoI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Uql0fQUHzl4doO5re6D8ni9ASq6eNneMX2TJ6YzzW1gEid1+mkRVLHmImiVnpVhKm caAaXpWI9okL+zn3pKn1wyGZmQTfZJ/SGSt0Ujzv3mY3bq7tyqJn3738+VRC6dNlVJ fiNa6B2+hdG5Nm3PV+a7113+Qfhy7GTUHWBlIJbCAnK83tU4Kx7WSVDso/+iEt9p3R fq8n9HKjbq0Dgl1XYipYolb+2AUFdxTpgsRqCrt1FmJtRb9JfO12EODzLXHQynVnkb yNn1yrVNT48Fst1YOKmdtwo2RdSL+rH9EGVJzFioWg++Xt++n2ZKOySzepbHiXE1pJ UIyVW4Kutq9Rw== List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 31 May 2023 15:11:15 +0200 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= To: Mark Millard Cc: freebsd-arm@freebsd.org, kevans@freebsd.org Subject: Re: devel/arm-none-eabi-newlib headers inconsistencies (not functional) or am I misusing something? In-Reply-To: <572F38A8-67ED-4A77-A5EC-C431141BF386@yahoo.com> References: <11a941a3a1c9e001559ccc6183af131d@mail.yourbox.net> <784313c52e2f42eb63f3755a5c093fdc@mail.yourbox.net> <9E888138-D3D0-4A6C-92B9-31705D470089@yahoo.com> <232dc6e4e0d3b5f3abcd37049db0991b@mail.yourbox.net> <8A93F4D2-4FDA-4C3D-8FA3-2D72DAD06A8B@yahoo.com> <572F38A8-67ED-4A77-A5EC-C431141BF386@yahoo.com> Message-ID: <65ed005700693855d4b0bc689aef0cc0@mail.yourbox.net> X-Sender: fbl@aoek.com User-Agent: Roundcube Webmail/1.2.0 X-Spamd-Result: default: False [-2.41 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_MIXED_CHARSET(0.59)[subject]; DMARC_POLICY_ALLOW(-0.50)[aoek.com,reject]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[aoek.com:s=mailbox]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[aoek.com:+]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2001:41d0:1:767d::1:server fail]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QWV5Y07Qxz45Df X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hi, El 2023-05-27 15:21, Mark Millard escribió: > On May 27, 2023, at 05:27, Mark Millard wrote: > It is unclear what you are doing for linking. Linking is another chapter that will be written after we can obtain objects. For the time being I am buinding a number of tests to see if the headers are functional or not, following your suggestion to add newlib ports header path first, and then arm-noabi-gcc header paths. I.e. #include <...> search starts here: /usr/local/arm-none-eabi/include /usr/local/lib/gcc/arm-none-eabi/11.3.0/include /usr/local/lib/gcc/arm-none-eabi/11.3.0/include-fixed End of search list. In this scenario the next problem I am hitting is this one: % arm-none-eabi-gcc test_stdatomic.c -c -g -DDEBUG -pipe -nostdinc -isystem /usr/local/arm-none-eabi/include -isystem /usr/local/lib/gcc/arm-none-eabi/11.3.0/include -isystem /usr/local/lib/gcc/arm-none-eabi/11.3.0/include-fixed -o test_stdatomic.o In file included from test_stdatomic.c:2: /usr/local/arm-none-eabi/include/stdatomic.h: In function 'atomic_flag_test_and_set_explicit': /usr/local/arm-none-eabi/include/stdatomic.h:386:17: error: request for member '__val' in something not a structure or union 386 | return (atomic_exchange_explicit(&__object->__flag, 1, __order)); | ^~~~~~~~~~~~~~~~~~~~~~~~ /usr/local/arm-none-eabi/include/stdatomic.h: In function 'atomic_flag_clear_explicit': /usr/local/arm-none-eabi/include/stdatomic.h:393:9: error: request for member '__val' in something not a structure or union 393 | atomic_store_explicit(&__object->__flag, 0, __order); | ^~~~~~~~~~~~~~~~~~~~~ % cat test_stdatomic.c #include #include int main(int argc, char *argv[]) { return 0; } Any suggestion before I patch /usr/local/arm-none-eabi/include/stdatomic.h to make it work? Thank you. BR, -- José Pérez