This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ABI attributes changes entry
> Gerald Pfeifer wrote:
>
> >Is there any particular reason to remove the reference to Wine? I do not
> >feel strongly about it, but examples are always nice. On the other hand,
> >Wine doesn't currently use this, right?, so it may not be a good example.
>
> I've got nothing against Wine, but I don't think it adds much. People
> who don't know what it is don't learn anything, and people who do may
> not get the point. An example is nice, but I'd rather it be spelled
> out, than just a reference. ("If you need to write code using the
> Microsoft ABI from with a GNU/Linux application, you could use this
> attribute on the Microsoft ABI functions, but still link to the GNU C
> Library, which, of course, uses the GNU/Linux ABI.")
Hi,
does this seem appropriate now?
Honza
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/changes.html,v
retrieving revision 1.19
diff -u -r1.19 changes.html
--- changes.html 23 Jul 2008 10:28:32 -0000 1.19
+++ changes.html 25 Jul 2008 11:56:27 -0000
@@ -161,8 +171,13 @@
<li>GCC can now utilize the SVML library for vectorizing calls to
a set of C99 functions if <code>-mveclibabi=svml</code> is specified
and you link to an SVML ABI compatible library.</li>
+ <li>In 64-bit mode, calling convention can be specified via <code>ms_abi</code>
+ (used by Microsoft Windows) and <code>sysv_abi</code> (used by
+ everything but Windows). If you need to write code using the Microsoft
+ ABI from with a GNU/Linux application, you could use this attribute on
+ the Microsoft ABI functions, but still link to the GNU C Library,
+ which, of course, uses the GNU/Linux ABI.
<li>A new <code>option</code> attribute was added to allow programmers to change the target options like <code>-msse2</code> or <code>-march=k8</code> for an individual function. You can also change the target options via the <code>GCC option</code> pragma for functions defined after the pragma.</li>
-
</ul>
<h3>MIPS</h3>