public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/46804] [4.5/4.6 Regression] gfortran.dg/char_cshift_2.f90 FAILs with -fregmove Date: Mon, 06 Dec 2010 14:56:00 -0000 [thread overview] Message-ID: <bug-46804-4-hLe3pktmly@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46804-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46804 --- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> 2010-12-06 14:56:13 UTC --- There are two likely related failures, but they both need -fno-tree-ter: gfortran.dg/char_eoshift_[24].f90 $ gfortran -O -fPIC -fexpensive-optimizations -fgcse -foptimize-register-move -fpeel-loops -fno-tree-loop-optimize -fno-tree-ter char_eoshift_2.f90 && ./a.out Aborted $ gfortran -O -fPIC -fexpensive-optimizations -fgcse -foptimize-register-move -fpeel-loops -fno-tree-loop-optimize -fno-tree-ter char_eoshift_4.f90 && ./a.out Aborted Neither of them fails in 4.4.
next prev parent reply other threads:[~2010-12-06 14:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-04 19:49 [Bug rtl-optimization/46804] New: " zsojka at seznam dot cz 2010-12-06 14:56 ` zsojka at seznam dot cz [this message] 2010-12-06 16:39 ` [Bug rtl-optimization/46804] " hjl.tools at gmail dot com 2010-12-08 10:50 ` jakub at gcc dot gnu.org 2010-12-08 11:17 ` jakub at gcc dot gnu.org 2010-12-08 11:54 ` jakub at gcc dot gnu.org 2010-12-10 16:41 ` jakub at gcc dot gnu.org 2010-12-10 16:47 ` [Bug rtl-optimization/46804] [4.5 " jakub at gcc dot gnu.org 2010-12-16 13:11 ` rguenth at gcc dot gnu.org 2011-01-16 20:20 ` jakub at gcc dot gnu.org 2011-01-17 8:28 ` jakub 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-46804-4-hLe3pktmly@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).