public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/95706] New test case gfortran.dg/pr95690.f90 fails
Date: Thu, 02 Jul 2020 07:02:20 +0000 [thread overview]
Message-ID: <bug-95706-4-hT5QNU4xpt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95706
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-07-02
Ever confirmed|0 |1
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
The interesting thing is that for a x86_64 -> aarch64-linux cross the error
_also_ appears on line 5:
> ./f951 -quiet /home/rguenther/src/gcc3/gcc/testsuite/gfortran.dg/pr95690.f90 -o pr95690.s -fno-diagnostics-show-caret
/home/rguenther/src/gcc3/gcc/testsuite/gfortran.dg/pr95690.f90:5:0: Error:
initializer for floating value is not a floating constant
so - what line number does the test report for a aarch64 -> x86_64-linux cross?
Note the error is emitted via output_constant via
4980 case REAL_TYPE:
4981 if (TREE_CODE (exp) != REAL_CST)
4982 error ("initializer for floating value is not a floating
constant");
so it depends on input_location (ick). Now the question is where on earth
input_location has a dependence on the host ...
On x86_64 the respective location is set via
New value = 2147483652
expand_gimple_stmt (stmt=<gimple_call 0x7ffff69dd260>)
at /home/rguenther/src/gcc3/gcc/cfgexpand.c:3847
3847 expand_gimple_stmt_1 (stmt);
(gdb) l
3842 it would be better if the diagnostic routines used the source
location
3843 embedded in the tree nodes rather than globals. */
3844 if (gimple_has_location (stmt))
3845 input_location = gimple_location (stmt);
3846
3847 expand_gimple_stmt_1 (stmt);
(gdb) p debug_gimple_stmt (stmt)
# .MEM_7 = VDEF <.MEM_6>
_gfortran_transfer_real_write (&dt_parm.0, &C.3905, 4);
which is where we expand C.3905 from.
next prev parent reply other threads:[~2020-07-02 7:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:06 [Bug testsuite/95706] New: " seurer at linux dot vnet.ibm.com
2020-06-17 6:32 ` [Bug testsuite/95706] " rguenth at gcc dot gnu.org
2020-06-17 14:54 ` seurer at linux dot vnet.ibm.com
2020-06-17 14:56 ` rguenther at suse dot de
2020-06-18 14:24 ` clyon at gcc dot gnu.org
2020-06-25 11:06 ` rguenth at gcc dot gnu.org
2020-06-25 11:06 ` rguenth at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
2020-07-02 7:02 ` rguenth at gcc dot gnu.org [this message]
2020-07-02 9:21 ` rguenth at gcc dot gnu.org
2020-07-02 21:08 ` ro at gcc dot gnu.org
2020-07-02 21:17 ` dje at gcc dot gnu.org
2020-07-03 10:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-12-14 16:33 ` danglin at gcc dot gnu.org
2023-04-02 15:41 ` danglin at gcc dot gnu.org
2023-04-29 16:35 ` vital.had 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-95706-4-hT5QNU4xpt@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).