public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54870] gfortran.dg/array_constructor_4.f90 FAILs Date: Fri, 12 Oct 2012 08:39:00 -0000 [thread overview] Message-ID: <bug-54870-4-Cpg98lOYN8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54870-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54870 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.guenther at gmail | |dot com --- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> 2012-10-12 08:39:33 UTC --- A reghunt revealed that this was caused by this patch: 2012-06-06 Richard Guenther <rguenther@suse.de> PR tree-optimization/53081 * tree-data-ref.h (adjacent_store_dr_p): Rename to ... (adjacent_dr_p): ... this and make it work for reads, too. * tree-loop-distribution.c (enum partition_kind): Add PKIND_MEMCPY. (struct partition_s): Change main_stmt to main_dr, add secondary_dr member. [...] It already occurs with a non-bootstrap gfortran and is independent of the libgfortran.so (built with our without the patch) used. I'm attaching the assembler outputs. Rainer
next prev parent reply other threads:[~2012-10-12 8:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 9:29 [Bug fortran/54870] New: " ro at gcc dot gnu.org 2012-10-09 9:30 ` [Bug fortran/54870] " ro at gcc dot gnu.org 2012-10-12 8:39 ` ro at gcc dot gnu.org [this message] 2012-10-13 21:33 ` [Bug fortran/54870] [4.8 regression] " ebotcazou at gcc dot gnu.org 2012-10-13 22:06 ` ebotcazou at gcc dot gnu.org 2012-10-16 22:49 ` [Bug rtl-optimization/54870] " ebotcazou at gcc dot gnu.org 2012-10-16 23:18 ` ebotcazou at gcc dot gnu.org 2012-10-16 23:19 ` ebotcazou 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-54870-4-Cpg98lOYN8@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).