diff options
| author | Guy Harris <guy@alum.mit.edu> | 2012-12-20 21:02:22 +0000 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2012-12-20 21:02:22 +0000 |
| commit | 6549d5a47f0ab0e3befc0a1af55d815d30c38301 (patch) | |
| tree | 1c9dc6c519094d11b7aeb4b8d422fe1f09c4a418 /configure.ac | |
| parent | 550c36d042c63053389dce37eb0f6f54e04155a6 (diff) | |
Expand the comment about alignment.
svn path=/trunk/; revision=46642
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index eecc665cba..03343d20ae 100644 --- a/configure.ac +++ b/configure.ac @@ -2028,7 +2028,11 @@ AC_SUBST(PLUGIN_LIBS) # I haven't been able to write C code that reliably makes that determination # (different versions of GCC with or without optimization give different # results) so just assume everything except (32-bit) x86 needs 8-byte -# alignment (64-bit x86 will get 8-byte alignment from G_MEM_ALIGN anyway). +# alignment (64-bit platforms either require 8-byte alignment for pointers +# and 64-bit integral data types or may get better performance from that; +# 64-bit x86 will get 8-byte alignment from G_MEM_ALIGN anyway. 32-bit +# platforms would only require it, or get better performance from it, +# for 64-bit floating-point values.). # AC_MSG_CHECKING(whether we need memory allocations to be 8-byte aligned) case $host_cpu in |