From: Yang Yujie <yangyujie@loongson.cn>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gcc-patches@gcc.gnu.org, Yang Yujie <yangyujie@loongson.cn>,
chenglulu@loongson.cn, xuchenghua@loongson.cn
Subject: Re: [PATCH v3 1/3] LoongArch: Adjust D version strings.
Date: Fri, 8 Dec 2023 09:50:33 +0800 [thread overview]
Message-ID: <qoj2eg5nvvs7jo2ixf7jzsapgz763lkpeloit3hxlnbg22pahi@ebi37n2tyahb> (raw)
In-Reply-To: <1701944777.1jwwfijhut.astroid@pulse.none>
On Thu, Dec 07, 2023 at 11:30:16AM +0100, Iain Buclaw wrote:
> Hi,
>
> Thanks for this.
>
> Excerpts from Yang Yujie's message of Dezember 1, 2023 11:08 am:
> > diff --git a/gcc/d/dmd/cond.d b/gcc/d/dmd/cond.d
> > index 568b639e0b6..02af0cc9e29 100644
> > --- a/gcc/d/dmd/cond.d
> > +++ b/gcc/d/dmd/cond.d
> > @@ -693,10 +693,10 @@ extern (C++) final class VersionCondition : DVCondition
> > case "LDC":
> > case "linux":
> > case "LittleEndian":
> > - case "LoongArch32":
> > case "LoongArch64":
> > - case "LoongArch_HardFloat":
> > - case "LoongArch_SoftFloat":
> > + case "LoongArch_F64":
> > + case "LoongArch_F32":
> > + case "LoongArch_SF":
> > case "MinGW":
> > case "MIPS32":
> > case "MIPS64":
>
> Changes to this module should be submitted to github.com/dlang/dmd,
> otherwise it'll get overwritten on the next "merge" with upstream.
>
> What's the rationale for F64 and SF abbreviations?
>
> Otherwise, looks reasonable.
>
> Iain.
Hi Iain,
Thanks for the review! I will push this to the dmd repo first shortly
and then send a v4 here.
By definition, LoongArch at the current stage can choose to implement either a
64-bit / 32-bit or no FPU at all, which are represented with target triplets
loongarch*-*{f64,f32.sf}. The F64/F32/SF-suffixed version strings represents
this distinction, though the support of the "F32" ISA variant is not active
upstream.
From what I can see, the current usage of "F64/SF" is only needed for FP
context code. I will also push the corresponding change to druntime later.
Also If you have the time, does the following patch look OK to you?
I couldn't get libphobos to build as a static library and this is the fix
I came up with.
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636767.html
Thanks,
Yujie
next prev parent reply other threads:[~2023-12-08 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:08 [PATCH v3 0/3] LoongArch D support Yang Yujie
2023-12-01 10:08 ` [PATCH v3 1/3] LoongArch: Adjust D version strings Yang Yujie
2023-12-07 10:30 ` Iain Buclaw
2023-12-08 1:50 ` Yang Yujie [this message]
2023-12-01 10:08 ` [PATCH v3 2/3] libphobos: Update build scripts for LoongArch64 Yang Yujie
2023-12-07 10:34 ` Iain Buclaw
2023-12-08 1:53 ` Yang Yujie
2023-12-01 10:08 ` [PATCH v3 3/3] libruntime: Add fiber context switch code for LoongArch Yang Yujie
2023-12-07 10:36 ` Iain Buclaw
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=qoj2eg5nvvs7jo2ixf7jzsapgz763lkpeloit3hxlnbg22pahi@ebi37n2tyahb \
--to=yangyujie@loongson.cn \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=ibuclaw@gdcproject.org \
--cc=xuchenghua@loongson.cn \
/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).