public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zajec5 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58092] BEQ (Branch on equal) jumps to wrong address (executes conditional code!)
Date: Wed, 07 Aug 2013 09:58:00 -0000 [thread overview]
Message-ID: <bug-58092-4-7vweVx6fJA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58092-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58092
--- Comment #7 from Rafał Miłecki <zajec5 at gmail dot com> ---
I compiled two versions of gcc on my own:
1) gcc-4.6.4.tar.bz2
2) gcc-linaro-4.6-2012.12.tar.bz2
For both of them I've used binutils-2.22.tar.bz2
test.o compiled with gcc-4.6.4.tar.bz2
00000000 <test>:
0: 24020002 li v0,2
4: aca20000 sw v0,0(a1)
8: 24020004 li v0,4
c: 14820002 bne a0,v0,18 <test+0x18>
10: 24020008 li v0,8
14: aca20040 sw v0,64(a1)
18: 03e00008 jr ra
1c: 00000000 nop
test.o compiled with gcc-linaro-4.6-2012.12.tar.bz2
00000000 <test>:
0: 24020002 li v0,2
4: 24030004 li v1,4
8: aca20000 sw v0,0(a1)
c: 10830002 beq a0,v1,18 <test+0x18>
10: 24020008 li v0,8
14: 8ca20040 lw v0,64(a1)
18: aca20040 sw v0,64(a1)
1c: 03e00008 jr ra
20: 00000000 nop
So it seems to be Linaro fault. I'll report that problem to them.
>From gcc-bugs-return-427510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Aug 07 10:09:01 2013
Return-Path: <gcc-bugs-return-427510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31095 invoked by alias); 7 Aug 2013 10:09:00 -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 30490 invoked by uid 48); 7 Aug 2013 10:08:28 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58098] wrong return value of normal_distribution::min()
Date: Wed, 07 Aug 2013 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58098-4-nJXIqc4KMm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58098-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: 2013-08/txt/msg00434.txt.bz2
Content-length: 337
http://gcc.gnu.org/bugzilla/show_bug.cgi?idX098
--- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Note: it's indeed debatable whether lowest or -infinity is better. For now I'm
going to minimally change our code to use lowest, because we use max the other
side, and infinities aren't unconditionally available.
next prev parent reply other threads:[~2013-08-07 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 12:06 [Bug c/58092] New: " zajec5 at gmail dot com
2013-08-06 12:08 ` [Bug c/58092] " zajec5 at gmail dot com
2013-08-06 12:17 ` zajec5 at gmail dot com
2013-08-06 12:51 ` mikpe at it dot uu.se
2013-08-06 14:43 ` zajec5 at gmail dot com
2013-08-06 16:42 ` mikpe at it dot uu.se
2013-08-06 21:28 ` [Bug target/58092] " zajec5 at gmail dot com
2013-08-07 9:58 ` zajec5 at gmail dot com [this message]
2013-08-07 10:41 ` zajec5 at gmail dot com
2013-08-07 10:42 ` zajec5 at gmail dot com
2013-08-07 13:51 ` zajec5 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-58092-4-7vweVx6fJA@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).