public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/102129] -ftrapping-math is broken or badly documented
Date: Tue, 31 Aug 2021 09:38:26 +0000	[thread overview]
Message-ID: <bug-102129-4-YoHhTx8z24@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102129-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:5e57bacf6f3599efea7634470db84121641c80b0

commit r12-3248-g5e57bacf6f3599efea7634470db84121641c80b0
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Aug 31 09:13:20 2021 +0200

    middle-end/102129 - avoid TER of possibly trapping expressions

    The following avoids applying TER to possibly trapping expressions,
    preventing a trapping FP multiplication to be moved across a call
    that should not be executed.

    2021-08-31  Richard Biener  <rguenther@suse.de>

            PR middle-end/102129
            * tree-ssa-ter.c (find_replaceable_in_bb): Do not move
            possibly trapping expressions across calls.

  parent reply	other threads:[~2021-08-31  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 14:32 [Bug middle-end/102129] New: " vincent-gcc at vinc17 dot net
2021-08-30 15:00 ` [Bug middle-end/102129] " vincent-gcc at vinc17 dot net
2021-08-30 19:49 ` joseph at codesourcery dot com
2021-08-31  0:37 ` vincent-gcc at vinc17 dot net
2021-08-31  7:12 ` rguenth at gcc dot gnu.org
2021-08-31  7:18 ` rguenth at gcc dot gnu.org
2021-08-31  8:25 ` rguenth at gcc dot gnu.org
2021-08-31  8:26 ` rguenth at gcc dot gnu.org
2021-08-31  8:49 ` rguenth at gcc dot gnu.org
2021-08-31  9:38 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-31  9:38 ` rguenth at gcc dot gnu.org

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-102129-4-YoHhTx8z24@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).