http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31696
--- Comment #8 from Drew 2012-10-31 03:55:13 UTC
---
After some googling I have found that ABI means application binary interface
and how this affects the problem, thank you.
I would be happy if someone could direct me to a tutorial on h
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31696
Dominique d'Humieres changed:
What|Removed |Added
CC||gnu.0kn at gishpuppy dot
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-04-25 22:58 ---
Yes the fortran standard does not define the ABI, the target which you are
compiling for does and if you change it in any way (which is what options like
-malign-double does) you are going to run into problems like t
--- Comment #5 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-25 22:46
---
I guess I walk away from you guys at this point. You need to think carefully
about the fortran standard, which does not define any abi whatsoever
(unfortunately). The fortran programmer is not supposed to think
--- Comment #4 from burnus at gcc dot gnu dot org 2007-04-25 19:58 ---
>From the man page:
"-malign-double
-mno-align-double
Control whether GCC aligns "double", "long double", and "long long" variables
on a two word boundary or a one word boundary. Aligning "double" variables on
a two
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-25 18:12 ---
Does not matter, this option changes the ABI, it is like any other ABI changing
option, you should not use it unless you understand what you are doing which is
clearly not the case.
--
pinskia at gcc dot gnu dot
--- Comment #2 from KnowlesPJ at Cardiff dot ac dot uk 2007-04-25 16:47
---
I don't understand your response, or the assumptions that might be behind it.
The program is standard fortran that compiles without warning, and I cannot see
why I would not want doubles aligned at 64 bits on x8
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-25 16:34 ---
what do you expect from an abi changing option?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
