This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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/RFA] PR gdb/648 (eval.c approval reqd)


I can see your point, and it's valid.

I was thinking of a very simple procedure:

proc deprecated_compile_with_gnu_fortran { program } { .... }

and have the fortran tests use that.

Attatched to the procedure would be a comment stating that anyone wanting to modify the testsuite to support non-GNU fortran will need to implement the infrastructure you describe described.

That way the fortran test directory can be populated with tests simultaneous to, or even prior to, adding the feature. While at the same time, establishing a very clear acceptance criteria for anyone wanting to hack things for non-GNU compilers.

how does this sound?
Andrew


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