This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] Re: GFortran testsuite problems with "dg-do compile"


Hi,

Brooks Moses schrieb:
>> I think, gfortran can live with "compile" and "run" only
> On the other hand, when a program contains no executable code -- for
> example, the main program is a no-op that merely uses several
> functions -- there's clearly no benefit to actually running the
> executable.
Therefore I wrote "can live" and not "should use". I think there are
cases, where it makes sense, but they are rather the exception than the
rule.

>> link:  char_result_11.f90
>> assemble: same_name_1.f90
>>
>> I converted the first one to a "run" and the second one to a "link" to
>> increase testing.
>
> I'm not sure I understand the reason for doing that -- if the intent
> is to not have "link" or "assemble" in the gfortran testsuite, why did
> you change the second one to "link"?  And, if that isn't the intent,
> what's the purpose of changing these at all, other than that they're
> there? (Even if that is the intent: Why is it useful?)
Well, for the first one: To make sure that the conversion actually works;

for the second one: To make sure that the two "u" don't clash, which is
detected at link time
000000000040067e T __m__u
0000000000400678 T __n__u

Especially for the first one, I'm not sure whether we could not manage
to break it.
The second one is fairly unlikely, but doing not only compiling but also
linking does not cost much time.

Tobias


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]