| Related articles |
|---|
| How to identify compilers robert.kahlert@aeg-hausgeraete.de (2003-01-30) |
| Re: How to identify compilers joachim_d@gmx.de (Joachim Durchholz) (2003-02-05) |
| Re: How to identify compilers chase@theworld.com (David Chase) (2003-02-05) |
| Re: How to identify compilers raffles2@att.net (Ron Ruble) (2003-02-05) |
| Re: How to identify compilers jgd@cix.co.uk (2003-02-06) |
| Re: How to identify compilers vbdis@aol.com (2003-02-06) |
| Re: How to identify compilers sandfeld@diku.dk (Allan Sandfeld Jensen) (2003-02-11) |
| Re: How to identify compilers aka@mvps.org (Alex K. Angelopoulos) (2003-02-21) |
| [1 later articles] |
| From: | Joachim Durchholz <joachim_d@gmx.de> |
| Newsgroups: | comp.compilers |
| Date: | 5 Feb 2003 23:53:02 -0500 |
| Organization: | Compilers Central |
| References: | 03-01-184 |
| Keywords: | practice |
| Posted-Date: | 05 Feb 2003 23:53:02 EST |
Robert wrote:
> Did anybody know, if (and how) it's possible to find out with which
> compiler a Windows executable file was compiled.
In general, this information isn't kept. (Actually it's impossible:
the linker may well combine modules written in different language into
a single executable.)
Of course, you can inspect the code and see whether it's typical for the
results of a specific compiler.
Regards,
Joachim
Return to the
comp.compilers page.
Search the
comp.compilers archives again.