Hi Andrew,
> This will break running the testsuite with an already installed compiler.
> Right now we don't need to have anything special in site.exp for running that.
> I do like the idea of automatic generating these but it does break a
> very important usage that some folks do already.
could you describe in detail how you run the testsuite in such a case?
In particular, is a build tree for the compiler under test still
available, including auto-host.h? If not, how was site.exp created for
such a testsuite run?
I've just noted that gen-et-static.awk is incomplete in several ways:
* It only handles the
#define <MACRO> <value>
case, but not
/* #undef <MACRO> */
* Even worse, if neither form is available, the
check_effective_target_<et> proc isn't generated at all, so you cannot
even generate a dummy et-static.exp from /dev/null.
I already wondered what to do when failing to load et-static.exp: right
now, it errors out. Otherwise, all uses of a generated effective target
would cause an error.
Besides, the original idea for generating et-static.exp involved gcc
dumping an equivalent of auto-host.h, either trivially just the textual
contents or in some pre-formatted form. This way the compiler config
would be self-describing. While this would work for compilers including
such a feature, it won't work for older ones obviously. I cannot tell
if/how we'd have to deal with such a case, though.
Comments?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
