public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67940] Wrong stack alignment adjustment
Date: Mon, 12 Oct 2015 17:28:00 -0000	[thread overview]
Message-ID: <bug-67940-4-caxf51pn0i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67940-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
This doesn't need a PR. Just commit the (pre-approved) obvious patch.
>From gcc-bugs-return-499357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 12 17:33:14 2015
Return-Path: <gcc-bugs-return-499357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56101 invoked by alias); 12 Oct 2015 17:33:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56074 invoked by uid 48); 12 Oct 2015 17:33:11 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/59412] __fixunsdfDI triggers wrong inexact exceptions
Date: Mon, 12 Oct 2015 17:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59412-4-UOdOZWrR90@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg00912.txt.bz2
Content-length: 471

https://gcc.gnu.org/bugzilla/show_bug.cgi?idY412

--- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Note that in addition to spurious "inexact" exceptions, this division can cause
spurious "underflow" exceptions when converting tiny values to integer 0.
Other spurious exceptions can occur in overflow cases, when only "invalid"
should be raised, and the signed conversions wrapping this function can fail to
raise "invalid" for some overflow cases.


  reply	other threads:[~2015-10-12 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 17:25 [Bug target/67940] New: " hjl.tools at gmail dot com
2015-10-12 17:28 ` ubizjak at gmail dot com [this message]
2015-10-12 17:36 ` [Bug target/67940] " hjl at gcc dot gnu.org
2015-10-12 17:38 ` hjl.tools at gmail dot com

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-67940-4-caxf51pn0i@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).