public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vital.had at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD
Date: Thu, 13 Jun 2024 09:51:59 +0000	[thread overview]
Message-ID: <bug-100662-4-0k84hU8Qmd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100662-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662

--- Comment #18 from Sergey Fedorov <vital.had at gmail dot com> ---
(In reply to Piotr Kubaj from comment #16)
> This issue has been fixed in FreeBSD's main branch on powerpc* in
> https://cgit.freebsd.org/src/commit/
> ?id=448c505c33cc334193590f3844406d6a74f26e2a
> 
> Similar fix could be done for other affected architectures.

Piotr, could you say, are there test results for the current gfortran on
FreeBSD ppc32 somewhere? To have some meaningful reference.

      parent reply	other threads:[~2024-06-13  9:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 19:13 [Bug fortran/100662] New: " yuri at tsoft dot com
2021-05-18 22:24 ` [Bug fortran/100662] " kargl at gcc dot gnu.org
2021-05-18 22:27 ` yuri at tsoft dot com
2021-05-18 22:47 ` yuri at tsoft dot com
2021-05-19  0:23 ` sgk at troutmask dot apl.washington.edu
2021-05-19  0:56 ` yuri at tsoft dot com
2021-05-19  1:10 ` sgk at troutmask dot apl.washington.edu
2021-05-19  1:43 ` yuri at tsoft dot com
2021-05-19  2:26 ` sgk at troutmask dot apl.washington.edu
2021-05-19  9:45 ` ripero84 at gmail dot com
2021-05-19 15:19 ` sgk at troutmask dot apl.washington.edu
2021-05-25 19:34 ` ripero84 at gmail dot com
2021-08-12 19:12 ` gerald at pfeifer dot com
2021-08-12 20:04 ` andreast at gcc dot gnu.org
2021-08-12 20:56 ` kargl at gcc dot gnu.org
2021-08-29 20:31 ` andreast at gcc dot gnu.org
2022-05-16 14:20 ` pkubaj at anongoth dot pl
2022-09-10 13:47 ` vital.had at gmail dot com
2024-06-13  9:51 ` vital.had at gmail dot com [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=bug-100662-4-0k84hU8Qmd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).