public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110311] [14 Regression] regression in tree-optimizer
Date: Thu, 29 Jun 2023 18:59:34 +0000 [thread overview]
Message-ID: <bug-110311-4-aqAMkkSXhr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110311-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110311
--- Comment #27 from anlauf at gcc dot gnu.org ---
(In reply to Jürgen Reuter from comment #26)
> It is included here:
> https://www.desy.de/~reuter/downloads/repro002.tar.xz
> I am working on a smaller example right now.
Good. I can reproduce the failure, but here's what others need to know:
- I have to
rm -f nlo_9_p2.i1.phs nlo_9_p2.m1.vg2
each time *before* running the test. ???
- I am using the modification to rng_stream_sub.f90 from comment#24 with the
printout added
- I am switching between
res = mod (x1, x2)
and
res = x1 - int(x1/x2) * x2
- I am disabling optimization completely for this file and added to Makefile:
rng_stream_sub.o: rng_stream_sub.f90
$(FC) $(FCFLAGS) -c $< -O0 -fdump-tree-original -fdump-tree-optimized
which gives (v1 is with intrinsic mod, v2 is with explicitly coded mod):
--- rng_stream_sub.f90.005t.original.v1 2023-06-29 20:44:58.148284991 +0200
+++ rng_stream_sub.f90.005t.original.v2 2023-06-29 20:45:45.408160849 +0200
@@ -3,7 +3,7 @@
{
real(kind=8) res;
- res = __builtin_fmod (*x1, *x2);
+ res = *x1 - (real(kind=8)) (integer(kind=4)) (*x1 / *x2) * *x2;
return res;
}
as expected. The dump-tree-optimized looks unsuspicious to me.
next prev parent reply other threads:[~2023-06-29 18:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 12:45 [Bug fortran/110311] New: [gfortran 14.0 regression] juergen.reuter at desy dot de
2023-06-20 6:29 ` [Bug fortran/110311] " juergen.reuter at desy dot de
2023-06-20 7:48 ` juergen.reuter at desy dot de
2023-06-20 8:08 ` [Bug fortran/110311] [14 Regression] gfortran 14.0 regression rguenth at gcc dot gnu.org
2023-06-20 10:13 ` juergen.reuter at desy dot de
2023-06-20 17:35 ` anlauf at gcc dot gnu.org
2023-06-20 17:38 ` juergen.reuter at desy dot de
2023-06-21 6:43 ` manolis.tsamis at vrull dot eu
2023-06-21 12:53 ` juergen.reuter at desy dot de
2023-06-21 23:37 ` pinskia at gcc dot gnu.org
2023-06-22 11:48 ` juergen.reuter at desy dot de
2023-06-22 11:54 ` [Bug fortran/110311] [14 Regression] regression in tree-optimizer juergen.reuter at desy dot de
2023-06-23 22:01 ` juergen.reuter at desy dot de
2023-06-23 23:23 ` juergen.reuter at desy dot de
2023-06-24 9:21 ` [Bug tree-optimization/110311] " juergen.reuter at desy dot de
2023-06-24 10:33 ` juergen.reuter at desy dot de
2023-06-24 11:47 ` anlauf at gcc dot gnu.org
2023-06-24 13:04 ` juergen.reuter at desy dot de
2023-06-24 13:09 ` juergen.reuter at desy dot de
2023-06-24 13:41 ` anlauf at gcc dot gnu.org
2023-06-24 13:43 ` juergen.reuter at desy dot de
2023-06-24 13:46 ` anlauf at gcc dot gnu.org
2023-06-24 18:21 ` anlauf at gcc dot gnu.org
2023-06-24 18:54 ` juergen.reuter at desy dot de
2023-06-24 19:16 ` anlauf at gcc dot gnu.org
2023-06-29 14:39 ` juergen.reuter at desy dot de
2023-06-29 17:29 ` anlauf at gcc dot gnu.org
2023-06-29 17:47 ` juergen.reuter at desy dot de
2023-06-29 18:59 ` anlauf at gcc dot gnu.org [this message]
2023-06-29 19:33 ` anlauf at gcc dot gnu.org
2023-06-29 19:35 ` juergen.reuter at desy dot de
2023-06-29 20:07 ` anlauf at gcc dot gnu.org
2023-06-30 17:45 ` anlauf at gcc dot gnu.org
2023-06-30 17:50 ` jakub at gcc dot gnu.org
2023-06-30 18:32 ` anlauf at gcc dot gnu.org
2023-06-30 18:57 ` anlauf at gcc dot gnu.org
2023-06-30 19:25 ` ubizjak at gmail dot com
2023-06-30 19:30 ` anlauf at gcc dot gnu.org
2023-06-30 19:32 ` anlauf at gcc dot gnu.org
2023-06-30 19:46 ` juergen.reuter at desy dot de
2023-06-30 19:47 ` ubizjak at gmail dot com
2023-06-30 20:19 ` anlauf at gcc dot gnu.org
2023-06-30 21:09 ` jakub at gcc dot gnu.org
2023-06-30 21:48 ` juergen.reuter at desy dot de
2023-07-01 7:55 ` anlauf at gcc dot gnu.org
2023-07-01 8:09 ` juergen.reuter at desy dot de
2023-07-06 19:40 ` juergen.reuter at desy dot de
2023-07-06 19:44 ` juergen.reuter at desy dot de
2023-07-06 21:18 ` anlauf at gcc dot gnu.org
2023-07-06 21:38 ` anlauf at gcc dot gnu.org
2023-07-07 12:44 ` juergen.reuter at desy dot de
2023-08-09 9:02 ` juergen.reuter at desy dot de
2023-08-09 9:24 ` jakub at gcc dot gnu.org
2023-08-25 21:17 ` juergen.reuter at desy dot de
2023-08-25 21:18 ` juergen.reuter at desy dot de
2023-08-25 21:23 ` juergen.reuter at desy dot de
2023-08-30 12:34 ` juergen.reuter at desy dot de
2023-09-22 14:56 ` juergen.reuter at desy dot de
2023-10-17 11:07 ` rguenth at gcc dot gnu.org
2024-03-27 13:41 ` rguenth 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-110311-4-aqAMkkSXhr@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).