This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/59674] On m68k and vax variables stack variables with > MAX_STACK_ALIGNMENT make ssp fail
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Jan 2015 18:56:47 +0000
- Subject: [Bug target/59674] On m68k and vax variables stack variables with > MAX_STACK_ALIGNMENT make ssp fail
- Auto-submitted: auto-generated
- References: <bug-59674-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59674
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
CC| |law at redhat dot com
--- Comment #10 from Jeffrey A. Law <law at redhat dot com> ---
As Andreas stated, having an ABI where the alignment of fundamental data types
is larger than the alignment of the stack will not work without significant
development.
Basically nothing guarantees that you stack is aligned enough to allow you to
then align those fundamental types on the stack.
To get the stack aligned properly you have to dynamically realigned the stack
at function entry, much like what's done for x86.
Without the dynamic stack alignment support, I would call the ABI used by
m68k-netbsd fundamentally broken. Sigh.
Downgrading to P5. m68k dynamic stack realignment isn't going to be a
priority.