Hi Tobias,
Bernd Schmidt wrote:
Does printf work? I thought I/O is not supported? Or does it just accept
it for linking and drop it? I think Janne's patch has already dealt with
the issue of stack allocation.
printf (or more accurately vprintf) is supported by ptx as a magic
builtin function. We have a printf wrapper around vprintf in our newlib.
And that prints to the normal screen? That makes debugging easier than I
had hoped for.
What was Janne's patch?
He changed stack allocation to static/heap allocation; the patch was
committed 36h ago, broke Cesar's bootstrap and is here:
https://gcc.gnu.org/ml/fortran/2014-11/msg00052.html
What I dislike a bit about the feature is that it is not clear what
features will be supported for LIBGFOR_MINIMAL. Maybe configure.ac would
be a good place to describe which features are included there (e.g. no
I/O but "printf" etc.) and which aren't. That will make it easier to see
what has to be modifed if one will add another differently bare system
later on.
My view is that it makes no sense to generalize this at the moment
when it is unknown what another target that uses this would look like.
The time to revisit this is when there is another target.
Well, one can still add some notes what is supported and what isn't –
not only for that hypothecial case but also when doing other changes to
the library (adding new functions).
Can't one write this differently, avoiding having most lines repeated
and only a few missing from the second set?
Modified. New patch below, how does this look? Regenerated files not
included. Testing in progress.
I like it more that way :-)
All in all: Okay when tesing succeeded. I still prefer some words what's
excluded (or included) in minimal as comment in configure.ac, but the
patch is also okay without.
Thanks,
Tobias
