From: Alexander Monakov <amonakov@ispras.ru>
To: Martin Uecker <muecker@gwdg.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: Concerns regarding the -ffp-contract=fast default
Date: Mon, 18 Sep 2023 18:38:27 +0300 (MSK) [thread overview]
Message-ID: <1a384baa-fe1c-2b36-03d8-42cc650b4e34@ispras.ru> (raw)
In-Reply-To: <0d101e3c2be84e4ff426615b910e6f513dbde0be.camel@gwdg.de>
On Mon, 18 Sep 2023, Martin Uecker wrote:
> > The hardest part would be popping the pragma state when leaving a block,
> > which didn't seem difficult (at least for C).
>
> It is fairly restricted where it can appear, it essentially operates
> on the level of compound statements (!= blocks).
Thanks for the clarification. Let me note that the standard somehow
decided to make out-of-place pragma a (compile-time) UB rather than
a constraint violation, leaving us free to make it work for blocks
(or launch Nethack).
Alexander
prev parent reply other threads:[~2023-09-18 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 16:48 Florian Weimer
2023-09-14 17:09 ` Alexander Monakov
2023-09-18 7:50 ` Alexander Monakov
2023-09-18 8:06 ` Richard Biener
2023-09-18 10:10 ` Florian Weimer
2023-09-18 10:37 ` Richard Biener
2023-09-18 11:37 ` Florian Weimer
2023-09-18 11:12 ` Alexander Monakov
2023-09-18 11:34 ` Florian Weimer
2023-09-18 11:55 ` Alexander Monakov
2023-09-18 16:41 ` Florian Weimer
2023-09-18 17:31 ` Alexander Monakov
2023-09-18 17:39 ` Joseph Myers
2023-09-18 11:26 ` Martin Uecker
2023-09-18 11:32 ` Jakub Jelinek
2023-09-18 11:43 ` Alexander Monakov
2023-09-18 12:13 ` Martin Uecker
2023-09-18 15:38 ` Alexander Monakov [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=1a384baa-fe1c-2b36-03d8-42cc650b4e34@ispras.ru \
--to=amonakov@ispras.ru \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=muecker@gwdg.de \
/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).