On 14/01/2014 16:54, Dmitri Gribenko wrote:
On Tue, Jan 14, 2014 at 2:51 PM, Alp Toker <[email protected]> wrote:
Author: alp
Date: Tue Jan 14 06:51:41 2014
New Revision: 199209
URL: http://llvm.org/viewvc/llvm-project?rev=199209&view=rev
Log:
Rename language option MicrosoftMode to MSVCCompat
There's been long-standing confusion over the role of these two options. This
commit makes the necessary changes to differentiate them clearly, following up
from r198936.
MicrosoftExt (aka. fms-extensions):
Enable largely unobjectionable Microsoft language extensions to ease
portability. This mode, also supported by gcc, is used for building software
like FreeBSD and Linux kernel extensions that share code with Windows drivers.
MSVCCompat (aka. -fms-compatibility, formerly MicrosoftMode):
Turn on a special mode supporting 'heinous' extensions for drop-in
compatibility with the Microsoft Visual C++ product. Standards-compilant C and
C++ code isn't guaranteed to work in this mode. Implies MicrosoftExt.
Note that full -fms-compatibility mode is currently enabled by default on the
Windows target, which may need tuning to serve as a reasonable default.
See cfe-commits for the full discourse, thread 'r198497 - Move MS predefined
type_info out of InitializePredefinedMacros'
Hi Alp,
Could you put this summary somewhere in the LanguageExtensions.rst or
in the manpage?
Good idea Dmitri, this commit message does read like documentation.
In fact there's already user-oriented coverage in UsersManual.rst which
is more or less accurate. So my write-up might be better adapted as a
doc comment or section in InternalsManual.rst.
The situation on the ground is changing rapidly so will hold back a few
days on this.
Alp.
--
http://www.nuanti.com
the browser experts
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
