From: Mike Stump <mikestump@comcast.net>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Janis Johnson <janis_johnson@mentor.com>,
gcc-patches@gcc.gnu.org, ro@cebitec.uni-bielefeld.de
Subject: Re: [PATCH] gfortran testsuite: implicitly cleanup-modules
Date: Fri, 29 Jun 2012 05:43:00 -0000 [thread overview]
Message-ID: <5B5DC7FC-E0DC-41AE-9D27-E0F2114FB213@comcast.net> (raw)
In-Reply-To: <20120629001525.GA8768@mx.loc>
On Jun 28, 2012, at 5:15 PM, Bernhard Reutner-Fischer wrote:
> On Thu, Jun 28, 2012 at 04:43:05PM -0700, Mike Stump wrote:
>> On Jun 28, 2012, at 3:27 PM, Bernhard Reutner-Fischer wrote:
>>> Perhaps you want to pursue this? We'd need to suggest this to dejagnu,
>>
>> Actually, we have the technology, so that isn't necessary. :-) You can install replacements for any procs you want, not pretty, but... it does work. I think this is a more deterministic path forward than waiting for a mythical dejagnu release. Also, we then can avoid the hassle of requiring a new dejagnu.
>
> Wouldn't that mean that we have to completely replace proc load_lib?
Yes; worse, it is a cut-n-paste from dejagnu and can effectively rev lock us to the current dejagnu release... One can delegate, but I don't think any pre or post processing in this case is enough to `fix' the issue, so it would be a wholesale replacement.
> But anyway.
> Mike, it would be nice if you could fix
>> +# BUG: gcc-dg calls gcc-set-multilib-library-path but does not load gcc-defs!
Sounds like a single line fix. It is the testing of that fix that is the annoying part.
next prev parent reply other threads:[~2012-06-29 2:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 21:40 [patch, testsuite, committed] Clean up gfortran.dg leftover module files Brooks Moses
2007-03-26 21:45 ` FX Coudert
2007-03-27 17:24 ` Bernhard Fischer
2007-03-27 17:29 ` Bernhard Fischer
2012-03-01 21:10 ` [PATCH] gfortran testsuite: implicitly cleanup-modules Bernhard Reutner-Fischer
2012-03-09 0:04 ` Mikael Morin
2012-03-13 16:39 ` Bernhard Reutner-Fischer
2012-03-13 20:31 ` Mike Stump
2012-03-15 12:40 ` Bernhard Reutner-Fischer
2012-03-15 15:57 ` Richard Guenther
2012-03-15 16:56 ` Bernhard Reutner-Fischer
2012-03-15 19:36 ` Jakub Jelinek
2012-03-16 10:05 ` Bernhard Reutner-Fischer
2012-03-16 15:00 ` Bernhard Reutner-Fischer
2012-06-29 0:15 ` Bernhard Reutner-Fischer
2012-06-29 0:55 ` Mike Stump
2012-06-29 0:56 ` Bernhard Reutner-Fischer
2012-06-29 5:43 ` Mike Stump [this message]
2013-06-07 14:30 ` Bernhard Reutner-Fischer
2013-06-10 23:21 ` Ben Elliston
2012-03-19 17:36 ` Rainer Orth
2012-03-22 12:30 ` Bernhard Reutner-Fischer
2012-04-03 12:17 ` [PATCH] gfortran testsuite: implicitly cleanup-modules, part 2 Bernhard Reutner-Fischer
2012-04-03 12:58 ` Bernhard Reutner-Fischer
2012-04-13 10:51 ` PING " Bernhard Reutner-Fischer
2012-04-13 13:58 ` Mike Stump
2012-04-13 14:40 ` Bernhard Reutner-Fischer
2012-04-13 20:09 ` Mike Stump
2012-04-13 14:15 ` Mike Stump
2015-04-23 8:55 ` [PATCH] gfortran testsuite: implicitly cleanup-modules Bernhard Reutner-Fischer
2015-04-29 21:58 ` Joseph Myers
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=5B5DC7FC-E0DC-41AE-9D27-E0F2114FB213@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=janis_johnson@mentor.com \
--cc=rep.dot.nop@gmail.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).