The thing is, see, is gcc really doesn't spend that much time playing
with the bytes. According to Jim's profiles, 4.5% of the time is spent
playing with incoming bytes (yylex); after that we always play with
tokens (ints). Unfortunately there is no single output function making
it hard to say exactly how much time is spent that way, but I don't think
I'm off in saying it isn't much.
> Now neither bytes,
> nor the members of the various structures used in gcc internally,
> are necessarily long- or quadwords (i.e. 32 or 64 bit quantities).
I suppose they needn't have been but they are. Virtually everything
done inside of gcc once things are parsed are with pointers and longs.
No, the thing to do to make gcc faster is not to worry about the I/O,
but to improve the algorithms used in the optimization phases.
-- To unsubscribe: send e-mail to email@example.com with 'unsubscribe' as the subject. Do not send it to firstname.lastname@example.org
Copyright © 1995-1997 Red Hat Software. Legal notices