public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54350] [4.8 Regression] FAIL: gfortran.dg/realloc_on_assign_*.f90 -O (internal compiler error) at r190586
Date: Wed, 22 Aug 2012 20:50:00 -0000 [thread overview]
Message-ID: <bug-54350-4-gqW8ehcYWX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54350-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54350
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |burnus at gcc dot gnu.org
|gnu.org |
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-08-22 20:49:08 UTC ---
Yes, that's a side-effect of my recent patch - sorry. I know about the issue
since this morning, but I didn't manage to fix it as quickly as I had hoped
for. Debugging memory leaks and understanding the scalarizer took longer than
anticipated.
The simplest is to revert
http://gcc.gnu.org/ml/fortran/2012-08/msg00120.html
Some issues and a possible approach to fix them is given in
http://gcc.gnu.org/ml/fortran/2012-08/msg00131.html
and the reply
http://gcc.gnu.org/ml/fortran/2012-08/msg00133.html
I have a patch which is currently building, but with build fixes, other
changes, and regtesting it will probably take a while until it is ready.
next prev parent reply other threads:[~2012-08-22 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 16:25 [Bug fortran/54350] New: " dominiq at lps dot ens.fr
2012-08-22 20:00 ` [Bug fortran/54350] " hp at gcc dot gnu.org
2012-08-22 20:50 ` burnus at gcc dot gnu.org [this message]
2012-08-24 7:44 ` burnus at gcc dot gnu.org
2012-08-24 7:46 ` burnus at gcc dot gnu.org
2012-08-24 7:46 ` burnus 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-54350-4-gqW8ehcYWX@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).