Cross gcc Mailing List Archive

[Prev][Next][Index][Thread]

identify compilers




Along the same lines, I sent this note to gnu.gcc.bug


Return-Path: leisner@sdsp.mc.xerox.com 
Return-Path: leisner
Received: from gnu.sdsp.mc.xerox.com (gnu.sdsp.mc.xerox.com [13.231.133.90]) by gemini.sdsp.mc.xerox.com (8.7.6/8.7.5) with SMTP id NAA22235 for <leisner>; Mon, 7 Oct 1996 13:35:26 -0400 (EDT)
Received: by gnu.sdsp.mc.xerox.com (4.1/client-1.3)
	id AA13097; Mon, 7 Oct 96 13:35:25 EDT
Date: Mon, 7 Oct 96 13:35:25 EDT
Message-Id: <9610071735.AA13097@gnu.sdsp.mc.xerox.com>
Mime-Version: 1.0
X-Newsreader: knews 0.9.8
Reply-To: leisner@sdsp.mc.xerox.com
Organization: xerox
From: leisner@sdsp.mc.xerox.com (Marty Leisner)
Subject:  identify-revision should be global?
Newsgroups: gnu.gcc.bug
Cc: leisner@sdsp.mc.xerox.com
Content-Type: text/plain; charset=us-ascii


Looking at the gcc 2.7.2 code and info file, I see:
(under m88k)
- -midentify-revision'
     Include an `ident' directive in the assembler output recording the
     source file name, compiler name and version, timestamp, and
     compilation flags used.

I haven't used this, but I had somethin in mind  which would make
the object file with the compiler and the options.

Why is this only in the m88k port...it seems far more general...

I suppose all assembler files have a way to comment something...it
seems it should be pretty generic.

- -- 
marty
leisner@sdsp.mc.xerox.com  
Member of the League for Programming Freedom

------- End of Forwarded Message



Home | Subject Index | Thread Index