public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64432] [5 Regression] SYSTEM_CLOCK(COUNT_RATE=rate) wrong result for integer(4)::rate Date: Tue, 30 Dec 2014 10:05:00 -0000 [thread overview] Message-ID: <bug-64432-4-hycizfDjO2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64432-4@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2846 bytes --] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64432 --- Comment #9 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> --- reading the standard, indeed it seems like count_rate can be real as well... same rules here *4 -> _4 *8 -> _8. As a side remark the following generates a slightly outdated error: > cat test.f90 COMPLEX(KIND=4) :: count_rate CALL SYSTEM_CLOCK(count_rate=count_rate) END > gfortran test.f90 test.f90:2:29: CALL SYSTEM_CLOCK(count_rate=count_rate) 1 Error: âcount_rateâ argument of âsystem_clockâ intrinsic at (1) must be INTEGER should be 'INTEGER or REAL'. count and count_max are still integer. >From gcc-bugs-return-471920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 30 10:57:03 2014 Return-Path: <gcc-bugs-return-471920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18453 invoked by alias); 30 Dec 2014 10:57:02 -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 18415 invoked by uid 48); 30 Dec 2014 10:56:57 -0000 From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64434] [5 Regression] Performance regression after operand canonicalization (r216728). Date: Tue, 30 Dec 2014 10:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ysrumyan at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: <bug-64434-4-1BJHO4akTh@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64434-4@http.gcc.gnu.org/bugzilla/> References: <bug-64434-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: 2014-12/txt/msg02927.txt.bz2 Content-length: 310 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd434 --- Comment #11 from Yuri Rumyantsev <ysrumyan at gmail dot com> --- Created attachment 34363 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id4363&actioníit patch to fix issue This patch fixed almost all issues related to operand canonicalization.
next prev parent reply other threads:[~2014-12-30 10:05 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-29 10:44 [Bug fortran/64432] New: " anlauf at gmx dot de 2014-12-29 11:14 ` [Bug fortran/64432] " anlauf at gmx dot de 2014-12-29 11:18 ` anlauf at gmx dot de 2014-12-29 11:20 ` janus at gcc dot gnu.org 2014-12-29 11:21 ` janus at gcc dot gnu.org 2014-12-29 14:13 ` fxcoudert at gcc dot gnu.org 2014-12-29 15:04 ` anlauf at gmx dot de 2014-12-29 15:23 ` anlauf at gmx dot de 2014-12-30 9:48 ` Joost.VandeVondele at mat dot ethz.ch 2014-12-30 10:05 ` Joost.VandeVondele at mat dot ethz.ch [this message] 2015-01-04 21:47 ` anlauf at gmx dot de 2015-01-04 21:56 ` anlauf at gmx dot de 2015-01-04 22:04 ` fxcoudert at gcc dot gnu.org 2015-01-04 22:53 ` anlauf at gmx dot de 2015-01-09 11:20 ` rguenth at gcc dot gnu.org 2015-01-09 14:12 ` jakub at gcc dot gnu.org 2015-01-19 20:49 ` anlauf at gmx dot de 2015-02-11 21:20 ` jvdelisle at gcc dot gnu.org 2015-02-13 22:31 ` anlauf at gmx dot de 2015-02-15 4:59 ` jvdelisle at gcc dot gnu.org 2015-02-16 3:14 ` jvdelisle at gcc dot gnu.org 2015-02-16 12:04 ` anlauf at gmx dot de 2015-02-16 20:04 ` jvdelisle at gcc dot gnu.org 2015-02-18 4:21 ` jvdelisle at gcc dot gnu.org 2015-02-18 20:04 ` anlauf at gmx dot de 2015-02-18 20:12 ` anlauf at gmx dot de 2015-02-19 16:32 ` jvdelisle at gcc dot gnu.org 2015-02-20 17:11 ` jvdelisle at gcc dot gnu.org 2015-02-20 22:14 ` anlauf at gmx dot de 2015-02-22 12:06 ` dominiq at lps dot ens.fr 2015-02-22 12:56 ` dominiq at lps dot ens.fr 2015-02-22 17:11 ` jvdelisle at gcc dot gnu.org 2015-02-26 17:44 ` jvdelisle at gcc dot gnu.org 2015-03-15 21:29 ` anlauf at gmx dot de 2015-03-17 1:02 ` jvdelisle at gcc dot gnu.org 2015-03-17 1:05 ` jvdelisle at gcc dot gnu.org 2015-03-17 1:22 ` jvdelisle at gcc dot gnu.org 2015-03-17 21:16 ` anlauf at gmx dot de 2015-03-17 22:33 ` jvdelisle at gcc dot gnu.org 2015-03-18 1:47 ` jvdelisle at gcc dot gnu.org 2015-03-20 7:38 ` jvdelisle 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-64432-4-hycizfDjO2@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: linkBe 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).