[Bug c++/116319] std::fma doesn't compute std::bfloat16_t as if to infinite precision and rounded only once.

2024-08-10 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116319 SHIH YEN-TE changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug c++/116319] std::fma doesn't compute std::bfloat16_t as if to infinite precision and rounded only once.

2024-08-10 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116319 SHIH YEN-TE changed: What|Removed |Added Summary|std::fma should compute as |std::fma doesn't compute

[Bug c++/116319] std::fma should compute as if to infinite precision and rounded only once to fit the result type.

2024-08-10 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116319 SHIH YEN-TE changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c++/116319] std::fma should compute as if to infinite precision and rounded only once to fit the result type.

2024-08-10 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116319 --- Comment #4 from SHIH YEN-TE --- I see, thank you. So, sounds like that if I don't implement the math by myself. For this case, we don't have a STL function to get the answer looks like infinite precision without doing rounding twice? In oth

[Bug c++/116319] New: std::fma should compute as if to infinite precision and rounded only once to fit the result type.

2024-08-09 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116319 Bug ID: 116319 Summary: std::fma should compute as if to infinite precision and rounded only once to fit the result type. Product: gcc Version: 14.1.0 Status: UNCONFIRME

[Bug c++/107834] #pragma GCC diagnostic ignored "-Wno-psabi" doe not work

2022-11-23 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107834 SHIH YEN-TE changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug c++/107834] New: #pragma GCC diagnostic ignored "-Wno-psabi" doe not work

2022-11-23 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107834 Bug ID: 107834 Summary: #pragma GCC diagnostic ignored "-Wno-psabi" doe not work Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Pr

[Bug libstdc++/106665] Cannot pass barrier by reference

2022-10-09 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106665 --- Comment #5 from SHIH YEN-TE --- Thanks, call pool.clear(); works.

[Bug libstdc++/106665] Cannot pass barrier by reference

2022-10-09 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106665 --- Comment #4 from SHIH YEN-TE --- You are right, I didn't notice it as well. Thanks for pointing it out.

[Bug c++/106665] Cannot pass barrier by reference

2022-08-17 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106665 --- Comment #1 from SHIH YEN-TE --- Another workaround is swap the declaration order of variable pool and sync_point. Changed from vector pool; barrier sync_point(8); To barrier sync_point(8); vector pool; Then the Segmentat

[Bug c++/106665] New: Cannot pass barrier by reference

2022-08-17 Thread shihyente at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106665 Bug ID: 106665 Summary: Cannot pass barrier by reference Product: gcc Version: 12.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++