public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tsu.yubo at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29858] New: Add more FPU_MASK_* for riscv64
Date: Tue, 06 Dec 2022 11:45:27 +0000	[thread overview]
Message-ID: <bug-29858-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29858

            Bug ID: 29858
           Summary: Add more FPU_MASK_* for riscv64
           Product: glibc
           Version: 2.36
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: tsu.yubo at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Hi,

The issue arises from when to build
[FETK](https://github.com/Electrostatics/FETK/issues/71#issuecomment-1144889677)
on riscv64 :

```
/<<PKGBUILDDIR>>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:17:
error: ‘_FPU_MASK_I’ undeclared (first use in this function)
  305 |         cw &= ~(_FPU_MASK_I | _FPU_MASK_Z | _FPU_MASK_O);
      |                 ^~~~~~~~~~~
/<<PKGBUILDDIR>>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:17: note:
each undeclared identifier is reported only once for each function it appears
in
/<<PKGBUILDDIR>>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:31:
error: ‘_FPU_MASK_Z’ undeclared (first use in this function)
  305 |         cw &= ~(_FPU_MASK_I | _FPU_MASK_Z | _FPU_MASK_O);
      |                               ^~~~~~~~~~~
/<<PKGBUILDDIR>>/debian/external_deps/fetk/punc/src/vf2c/uninit.c:305:45:
error: ‘_FPU_MASK_O’ undeclared (first use in this function)
  305 |         cw &= ~(_FPU_MASK_I | _FPU_MASK_Z | _FPU_MASK_O);
      |                                             ^~~~~~~~~~~
```
I know the `sysdeps/riscv/fpu_control.h` file has not been updated since it was
first introduced. Does it make sense to add support those macros for riscv64?
If so, I can try it. thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-12-06 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 11:45 tsu.yubo at gmail dot com [this message]
2022-12-06 12:30 ` [Bug libc/29858] " schwab@linux-m68k.org
2022-12-06 13:35 ` tsu.yubo at gmail dot com

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=bug-29858-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).