From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id 8B7453858D37; Sun, 20 Mar 2022 15:30:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8B7453858D37 Received: by mail-wr1-x42a.google.com with SMTP id r10so17777415wrp.3; Sun, 20 Mar 2022 08:30:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=X2LpOuUUPbKxaBtu0CP7brCdTOtURN8N0qoLp58ARkM=; b=7Y8Gd4WWI01PZSyZ9aHr1Z/I0jQXX0ZLso9w2cJLGSI5RDD7HEQRCnC9iNvh1a4wuu eatppWsF65exxOEL6eBHRdN70A7rk2RG623qEGWOZLoD3PCcSgy9P6MVQqqAW27p7we6 vf5cB+rihH2rregx/bs8toocDp1a5TEof/TDAZG3xiC1krmu2GApQ8jZ4Yaz41cW6UEo K2pYEWZSGfLaitCxqkzHS52cuRNRjsvWBds07uhMojowKa3nIOlIiqjDPXa6kv3NvL1d BBjwOMKu1PECLt3L6QfAhXK34DKd7C7CTkwMI9OXP+RFPABjxls/xf18TSHy2ffa0MXY BsFQ== X-Gm-Message-State: AOAM532rVhUCf3zECuprECM/m653qGu2ZqmiithtGJyKhXVzEDo5pv5m nbOoSFj73Vzm0vZLzUBtE0kWhERmugs= X-Google-Smtp-Source: ABdhPJwVfjvUU+usD+HMWzAQf7kghfJ5xW/0EX+dP+Sx4hTnASgy5Px7iVqRrX2Bku2h8vbD+0hJYQ== X-Received: by 2002:a5d:6c6b:0:b0:1ea:77ea:dde8 with SMTP id r11-20020a5d6c6b000000b001ea77eadde8mr15562473wrz.690.1647790209173; Sun, 20 Mar 2022 08:30:09 -0700 (PDT) Received: from smtpclient.apple ([2a01:e34:ec28:8cb0:4889:1024:3164:84d8]) by smtp.gmail.com with ESMTPSA id o11-20020adfe80b000000b00203dda2388dsm11160160wrm.30.2022.03.20.08.30.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Mar 2022 08:30:08 -0700 (PDT) From: FX Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd Message-Id: <2E9BFB96-6979-4DB5-8029-1F89C30B242B@gmail.com> Date: Sun, 20 Mar 2022 16:30:08 +0100 Cc: pkubaj@freebsd.org, segher@kernel.crashing.org To: gcc-patches@gcc.gnu.org, Fortran List X-Mailer: Apple Mail (2.3696.80.82.1.1) X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FAKE_REPLY_B, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, 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: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2022 15:30:12 -0000 Hi, (Please send all Fortran (front-end and libgfortran) patches in CC to = the Fortran list.) Please hold from pushing the patch as is, I have some questions: - If FreeBSD has feenableexcept() and related functions, it should = already use the fpu-glibc code, because of this: if test "x${have_feenableexcept}" =3D "xyes"; then fpu_host=3D'fpu-glibc' ieee_support=3D'yes' fi So before the patch, what was configure.host returning, and what is the = value of have_feenableexcept? - Why restrict the patch to powerpc*? Don=E2=80=99t other FreeBSD = targets have that function? - How does the patch affect the results of =E2=80=9Cmake = check-gfortran=E2=80=9D? Thanks, FX=