Nonrecursive build within gcc directory

Tim Josling tej@melbpc.org.au
Sun Oct 22 11:46:00 GMT 2000


> This patch rearranges the Makefiles so that we don't need to recurse
> into the language subdirectories. 

This is great. It will save having to put a lot of redundant
information, twice, in two places.

But is it really not possible to optionally turn off pedantic and
traditional for the front ends. Before I turned them off for my
nascent COBOL front end, I was getting thousands of entirely
useless messages. I am not planning to support a K&R compiler -
after all ANSI C has been around since the decade before last
(depending 
on how pedantic your definition of decades is) -
and I do not want to limit myself to features supported in K&R. 

As for pedantic I have never found any of these messages helpful
(others may I suppose).

A lot of the messages also relate to the output for flex and
bison and other utilities which I cannot control. 

By the way can anyone tell me how to get rid of the message

'int constants are signed in ansi unsigned in K&R' 

(or maybe its the other way around)? It seems to report the error
even when defining a constant that has the same effect regardless
of dialect - what is the point of the message? I don't like
warnings that can't be removed by any possible action (other than
definining your ints in hex which is worse than the disease).

Tim Josling

> This patch rearranges the Makefiles so that we don't need to recurse
> into the language subdirectories.


More information about the Gcc-patches mailing list