public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107436] Is -fsignaling-nans still experimental?
Date: Fri, 28 Oct 2022 11:53:54 +0000 [thread overview]
Message-ID: <bug-107436-4-ZsP36xaIMm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107436-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
The question is what the expectations are. I think that all issues would be
considered bugs (see the list of referenced bugs).
Can you evaluate it according to your needs and file bugreports for issues not
covered?
next prev parent reply other threads:[~2022-10-28 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 15:17 [Bug web/107436] New: " florian.schanda at bmw dot de
2022-10-27 15:27 ` [Bug middle-end/107436] " pinskia at gcc dot gnu.org
2022-10-28 5:32 ` florian.schanda at bmw dot de
2022-10-28 9:26 ` florian.schanda at bmw dot de
2022-10-28 11:53 ` rguenth at gcc dot gnu.org [this message]
2022-10-28 11:56 ` florian.schanda at bmw dot de
2022-10-28 14:21 ` jakub at gcc dot gnu.org
2022-11-29 9:54 ` florian.schanda at bmw dot de
2024-01-04 18:55 ` florian.schanda at bmw dot de
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-107436-4-ZsP36xaIMm@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).