From: "Tobias Schlüter" <tobias.schlueter@physik.uni-muenchen.de>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: Fortran List <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
joost.vandevondele@mat.ethz.ch
Subject: Re: PR fortran/51727: make module files reproducible, question on C++ in gcc
Date: Thu, 29 Nov 2012 10:40:00 -0000 [thread overview]
Message-ID: <50B73B98.4060301@physik.uni-muenchen.de> (raw)
In-Reply-To: <CAO9iq9FU6wu8n5kYN=36Z_JVO=guVb=XxGR_NSm5H81nVHMg6Q@mail.gmail.com>
Dear gfortraners,
On 2012-10-14 23:35, Janne Blomqvist wrote:
> - I'd be vary wrt backporting, in my experience the module.c code is
> somewhat fragile and easily causes regressions. In any case, AFAICS PR
> 51727 is not a regression.
Can this be reconsidered, as the benefits for users seem to be fairly
large? According to bugzilla, the patch didn't cause any regressions
after three weeks in the trunk. Joost has used this patch in
hand-patched 4.7 compilers for a few weeks more with no negative effects.
Cheers,
- Tobi
prev parent reply other threads:[~2012-11-29 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 13:41 Tobias Schlüter
2012-10-13 13:51 ` Tobias Schlüter
2012-10-13 18:21 ` Diego Novillo
2012-10-13 18:23 ` Tobias Schlüter
2012-10-13 18:23 ` Diego Novillo
2012-10-13 22:48 ` Joseph S. Myers
2012-10-14 22:37 ` Janne Blomqvist
2012-10-15 0:31 ` Jakub Jelinek
2012-10-15 12:54 ` Tobias Schlüter
2012-10-15 17:58 ` Tobias Schlüter
2012-10-15 21:06 ` [PATCH] Install error handler for out-of-memory when using STL containers " Tobias Schlüter
2012-10-28 15:50 ` Ping: [PATCH] Install error handler for out-of-memory when using STL containers Tobias Schlüter
2012-10-29 9:48 ` Paul Richard Thomas
2012-10-29 17:38 ` Mike Stump
2012-11-03 9:17 ` Ping**2: " Tobias Schlüter
2012-10-15 13:12 ` PR fortran/51727: make module files reproducible, question on C++ in gcc Tobias Schlüter
2012-11-08 19:02 ` Tobias Schlüter
2012-11-29 10:40 ` Tobias Schlüter [this message]
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=50B73B98.4060301@physik.uni-muenchen.de \
--to=tobias.schlueter@physik.uni-muenchen.de \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joost.vandevondele@mat.ethz.ch \
/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).