From: Gerald Pfeifer <gerald@pfeifer.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Document 3 changes in GCC 6
Date: Tue, 01 Mar 2016 23:19:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1603020016240.6772@anthias> (raw)
In-Reply-To: <8186265.USun8IfHWT@polaris>
On Mon, 29 Feb 2016, Eric Botcazou wrote:
> - new scalar_storage_order type attribute in C,
> - ABI change for SPARC 64-bit,
> - automatic enabling of -mstackrealign with SSE for Windows 32-bit.
+ <li>A new type attribute <code>scalar_storage_order</code> applying to
+ structures and unions has been introduced. It makes it possible
+ to specify the storage order (aka endianness) in memory of scalar
+ fields in the structures or unions.</li>
How about saying "It specifies the storage order..."?
And "in structures and unions"?
+ <li>An ABI bug has been fixed in 64-bit mode. Unfortunately, this change
+ will break binary compatibility with earlier releases for code it affects,
+ but this should be pretty rare in practice. The conditions are: a 16-byte
+ structure containing a <code>double</code> or a 8-byte vector in the second
+ half is passed in slot #15 to a subprogram, for example as 16th parameter
+ if the first 15 ones have at most 8 bytes. The <code>double</code> or
+ vector was wrongly passed in floating-point register <code>%d32</code>
+ in lieu of on the stack as per the SPARC calling conventions.</li>
That really must occur super, super rarely. ;-)
How about "...is passed to a subprogram in slot #15..."?
Okay with the changes above. Thanks for taking the time to
document these!
Gerald
next prev parent reply other threads:[~2016-03-01 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 10:36 Eric Botcazou
2016-03-01 23:19 ` Gerald Pfeifer [this message]
2016-03-01 23:28 ` Eric Botcazou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.20.1603020016240.6772@anthias \
--to=gerald@pfeifer.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).