Path: utzoo!utgpu!watmath!uunet!cs.utexas.edu!wuarchive!udel!princeton!phoenix!phoenix.princeton.edu!eho From: eho@clarity.Princeton.EDU (Eric Ho) Newsgroups: gnu.gcc Subject: putting architectural info outside gcc ? Message-ID: Date: 10 Sep 89 07:08:51 GMT Sender: news@phoenix.Princeton.EDU Distribution: gnu Organization: Cognitive Science Lab. Princeton University. Lines: 26 I was just thinking that since gcc is a retargetable optimizing compiler, wouldn't it be nice to put all kinds of architectural info outside the compiler -- i.e. in a seperate file or data/rule base of some sort and gcc reads this file according to what architecture the user is compiling his/her program on. This way, you save a lot of time by avoiding to rebuild gcc everytime you've need recompile your code for different architectures. For instance, if I want to remake my application for a new architecture then all I need to do is supply that architectural info/database to gcc and it'll generate the correct binary for that new architecture (without recompiling gcc at all) and I can do all this on my Sun-4 or do it on the new machine. What do others think ? It shouldn't be too difficult to reorgainize gcc this way, right ? -- Eric Ho Cognitive Science Lab., Princeton University voice = 609-258-2987 email = eho@confidence.princeton.edu 609-258-2819 (messages) eho@bogey.princeton.edu regards. -eric-