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 fortran/59313] gfortran.dg/erf_3.F90 FAILs on Solaris/SPARC
Date: Fri, 29 Nov 2013 18:48:00 -0000 [thread overview]
Message-ID: <bug-59313-4-0GAKyY9HnD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59313-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59313
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|sparc*-sun-solaris2.* |sparc*-sun-solaris2.*,
| |alpha-linux-gnu
CC| |ubizjak at gmail dot com
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Eric Botcazou from comment #1)
> I'm seeing this too.
Me to, on alpha-linux-gnu, exactly the same numbers:
0.00000000000000000000000000000000000
0.00000000000000000000000000000000000
0.00000000000000000000000000000000000
0.00000000000000000000000000000000000
0.00000000000000000000000000000000000
6167208123267181.00000000000000000000
Program aborted. Backtrace:
#0 0x2000004F197
>From gcc-bugs-return-436287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:54:21 2013
Return-Path: <gcc-bugs-return-436287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22406 invoked by alias); 29 Nov 2013 18:54:21 -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 22363 invoked by uid 48); 29 Nov 2013 18:54:17 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59313] gfortran.dg/erf_3.F90 FAILs on Solaris/SPARC
Date: Fri, 29 Nov 2013 18:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: NEW
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-59313-4-umv5BYTs2B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59313-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59313-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-11/txt/msg03064.txt.bz2
Content-length: 381
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59313
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Uroš Bizjak from comment #2)
> Me to, on alpha-linux-gnu, exactly the same numbers:
alpha-linux-gnu is 128 bit long double, but not __float128 target:
auto-host.h:#define TARGET_DEFAULT_LONG_DOUBLE_128 1
Probably sparc also defines this.
>From gcc-bugs-return-436288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:31:50 2013
Return-Path: <gcc-bugs-return-436288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12315 invoked by alias); 29 Nov 2013 19:31:49 -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 12263 invoked by uid 48); 29 Nov 2013 19:31:45 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59176] [4.9 Regression] ICE edge points to wrong declaration / verify_cgraph_node failed
Date: Fri, 29 Nov 2013 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59176-4-fik8dW1GkC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59176-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-11/txt/msg03065.txt.bz2
Content-length: 288
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY176
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Now that PR59208 was fixed, I tried the test case of this PR again (with
today's r205539).
Result: Still the same, an ICE with -O3 in verify_cgraph_node. (-O2 is fine.)
next prev parent reply other threads:[~2013-11-29 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 14:24 [Bug fortran/59313] New: " ro at gcc dot gnu.org
2013-11-29 18:48 ` ubizjak at gmail dot com [this message]
2013-12-01 19:31 ` [Bug libfortran/59313] " ubizjak at gmail dot com
2013-12-01 20:56 ` uros at gcc dot gnu.org
2013-12-01 21:00 ` ubizjak at gmail dot com
2013-12-13 22:17 ` ebotcazou at gcc dot gnu.org
2014-02-22 8:56 ` ebotcazou at gcc dot gnu.org
2014-02-25 9:28 ` ro at gcc dot gnu.org
2014-03-24 0:33 ` danglin 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-59313-4-0GAKyY9HnD@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).