public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Junxian Zhu <zhujunxian@oss.cipunited.com>
Cc: <libc-alpha@sourceware.org>, <rongrong@oss.cipunited.com>
Subject: Re: [PATCH 2/2] MIPS: Hard-float rounding instructions support
Date: Fri, 29 Dec 2023 01:00:31 +0000	[thread overview]
Message-ID: <2cdc9ad4-bf63-6de9-734-3497fb9921b@codesourcery.com> (raw)
In-Reply-To: <20231225103548.1615-4-zhujunxian@oss.cipunited.com>

On Mon, 25 Dec 2023, Junxian Zhu wrote:

> diff --git a/sysdeps/mips/mips32/Implies b/sysdeps/mips/mips32/Implies
> index 6473f2517c..71b3678c6c 100644
> --- a/sysdeps/mips/mips32/Implies
> +++ b/sysdeps/mips/mips32/Implies
> @@ -1,3 +1,4 @@
> +mips/fpu
>  mips/ieee754
>  mips
>  wordsize-32
> diff --git a/sysdeps/mips/mips64/Implies b/sysdeps/mips/mips64/Implies
> index 826ff1541f..8885ebd564 100644
> --- a/sysdeps/mips/mips64/Implies
> +++ b/sysdeps/mips/mips64/Implies
> @@ -1,4 +1,5 @@
>  # MIPS uses IEEE 754 floating point.
> +mips/fpu
>  mips/ieee754
>  ieee754/flt-32
>  ieee754/dbl-64

These changes are clearly incorrect, as they would cause mips/fpu/ to be 
used for soft-float.  The fpu/ directories are selected automatically for 
hard-float, and must not be used for soft-float.

I'm guessing you're motivated by some ordering issue that results in the 
ieee754/ directories ending up being used before mips/fpu/.  I'm not sure 
of the best way to avoid such an ordering issue (noting that the ieee754/ 
directories go in Implies separately for mips32 and mips64 because only 
mips64 uses ldbl-128), but e.g. #includes like in 
sysdeps/mips/mips64/n32/fpu/s_fma.c should work if you can't get the 
preferred sysdeps directory ordering.

-- 
Joseph S. Myers
joseph@codesourcery.com

      parent reply	other threads:[~2023-12-29  1:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25 10:35 [PATCH 0/2] Add hard-float rounding instructions support for MIPS architecture Junxian Zhu
2023-12-25 10:35 ` [PATCH 1/2] limb-alias-double.h: Fix missing semicolon Junxian Zhu
2023-12-25 10:35 ` [PATCH 2/2] MIPS: Hard-float rounding instructions support Junxian Zhu
2023-12-25 10:51   ` Xi Ruoyao
2023-12-26  2:37     ` Junxian Zhu
2023-12-26  8:29       ` Xi Ruoyao
2023-12-26 20:12         ` Adhemerval Zanella Netto
2023-12-26 21:50           ` Xi Ruoyao
2023-12-26 22:50             ` Xi Ruoyao
2023-12-27 13:25               ` Adhemerval Zanella Netto
2024-01-02 10:08               ` Junxian Zhu
2024-01-02  9:43         ` Junxian Zhu
2024-01-02  9:57           ` Xi Ruoyao
     [not found]         ` <5f0f4c83-f6d8-4af3-8cce-e12cd5314da1@oss.cipunited.com>
2024-01-31  9:08           ` Xi Ruoyao
2024-01-25 13:58     ` Junxian Zhu
2024-01-25 14:37       ` Xi Ruoyao
2023-12-25 12:36   ` YunQiang Su
2023-12-26  2:48     ` Junxian Zhu
2024-01-02  9:51     ` Junxian Zhu
2023-12-29  1:00   ` Joseph Myers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cdc9ad4-bf63-6de9-734-3497fb9921b@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rongrong@oss.cipunited.com \
    --cc=zhujunxian@oss.cipunited.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).