[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da37664a0ed2c23bc7139eb0d8c6a286@smtp.hushmail.com>
Date: Tue, 26 Jun 2012 09:49:32 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: john --list=build-version shows gcc version info even
if built with clang
On 2012-06-26 08:30, Frank Dittrich wrote:
> I'm not sure whether we should "fix" this, apparently clang defines
> __GNUC__* to indicate gcc compatibility. May be some clang expert knows
> what else to check to aditionally identify the clang version?
>
> This should avoid any confusion with a gcc 4.2.1 version:
> Build: linux-x86-64-clang
>
> So there is no urgent need to "fix" the output.
Ideally we should see the version of the actual compiler but this is
lower prio right now.
$ clang -v
Ubuntu clang version 3.0-6ubuntu3 (tags/RELEASE_30/final) (based on LLVM
3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
$ clang -dM -E -x c /dev/null | fgrep '3.0'
#define __VERSION__ "4.2.1 Compatible Ubuntu Clang 3.0
(tags/RELEASE_30/final)"
#define __clang_version__ "3.0 (tags/RELEASE_30/final)"
We should use __clang_version__ if defined, and if not we can use
__GNUC__*. But before fixing this, the same should be determined for icc.
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
