public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61876] Converting __builtin_round + cast into __builtin_lround is not always equivalent in regards to math errno
Date: Fri, 25 Jul 2014 09:09:00 -0000	[thread overview]
Message-ID: <bug-61876-4-AW8YjeKn7h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61876-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #8 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to ktkachov from comment #7)
> (In reply to joseph@codesourcery.com from comment #6)
> > Under Annex F the cast isn't undefined behavior but raising the "invalid" 
> > exception and returning an unspecified value (which must be a valid value 
> > of type long, i.e. the program must behave as if each execution of the 
> > cast in the abstract machine has some particular value of type long it 
> > returns).
> 
> In my copy at 6.3.1.4 on Real floating and integer conversions it says:
> If the value of the integral part cannot be represented by the integer type,
> the behavior is undefined.

Making Annex F explicitly take precedence over the generic text is DR#442.


  parent reply	other threads:[~2014-07-25  9:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 11:08 [Bug tree-optimization/61876] New: " ktkachov at gcc dot gnu.org
2014-07-22 11:11 ` [Bug middle-end/61876] " ktkachov at gcc dot gnu.org
2014-07-23 12:19 ` rguenth at gcc dot gnu.org
2014-07-23 13:04 ` ktkachov at gcc dot gnu.org
2014-07-24 13:23 ` ktkachov at gcc dot gnu.org
2014-07-24 13:29 ` ktkachov at gcc dot gnu.org
2014-07-24 21:12 ` joseph at codesourcery dot com
2014-07-25  9:07 ` ktkachov at gcc dot gnu.org
2014-07-25  9:09 ` mpolacek at gcc dot gnu.org [this message]
2014-07-25 13:45 ` joseph at codesourcery dot com
2014-08-05  9:53 ` ktkachov at gcc dot gnu.org
2014-08-05  9:58 ` ktkachov 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-61876-4-AW8YjeKn7h@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).