public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/29858] New: Add more FPU_MASK_* for riscv64
@ 2022-12-06 11:45 tsu.yubo at gmail dot com
2022-12-06 12:30 ` [Bug libc/29858] " schwab@linux-m68k.org
2022-12-06 13:35 ` tsu.yubo at gmail dot com
0 siblings, 2 replies; 3+ messages in thread
From: tsu.yubo at gmail dot com @ 2022-12-06 11:45 UTC (permalink / raw)
To: glibc-bugs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/29858] Add more FPU_MASK_* for riscv64
2022-12-06 11:45 [Bug libc/29858] New: Add more FPU_MASK_* for riscv64 tsu.yubo at gmail dot com
@ 2022-12-06 12:30 ` schwab@linux-m68k.org
2022-12-06 13:35 ` tsu.yubo at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: schwab@linux-m68k.org @ 2022-12-06 12:30 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29858
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |NOTABUG
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
RISC-V does not implement fpu exception traps, it only provides accrued
exception flags.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/29858] Add more FPU_MASK_* for riscv64
2022-12-06 11:45 [Bug libc/29858] New: Add more FPU_MASK_* for riscv64 tsu.yubo at gmail dot com
2022-12-06 12:30 ` [Bug libc/29858] " schwab@linux-m68k.org
@ 2022-12-06 13:35 ` tsu.yubo at gmail dot com
1 sibling, 0 replies; 3+ messages in thread
From: tsu.yubo at gmail dot com @ 2022-12-06 13:35 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29858
--- Comment #2 from Bo YU <tsu.yubo at gmail dot com> ---
Ok, thanks for the explanations.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-12-06 13:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-06 11:45 [Bug libc/29858] New: Add more FPU_MASK_* for riscv64 tsu.yubo at gmail dot com
2022-12-06 12:30 ` [Bug libc/29858] " schwab@linux-m68k.org
2022-12-06 13:35 ` tsu.yubo at gmail dot com
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).