public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59674] On m68k and vax variables stack variables with > MAX_STACK_ALIGNMENT make ssp fail
Date: Fri, 16 Jan 2015 18:56:00 -0000 [thread overview]
Message-ID: <bug-59674-4-KbeTNBcRZC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59674-4@http.gcc.gnu.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.
next prev parent reply other threads:[~2015-01-16 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 4:14 [Bug c/59674] New: " christos at zoulas dot com
2014-01-04 11:20 ` [Bug c/59674] " mikpelinux at gmail dot com
2014-01-04 17:22 ` mikpelinux at gmail dot com
2014-01-04 19:31 ` christos at zoulas dot com
2014-01-04 20:42 ` mikpelinux at gmail dot com
2014-01-04 21:21 ` christos at zoulas dot com
2014-01-04 21:49 ` schwab@linux-m68k.org
2014-01-23 17:12 ` martin at netbsd dot org
2014-01-24 21:37 ` [Bug target/59674] " schwab@linux-m68k.org
2015-01-16 18:56 ` law at redhat dot com [this message]
2015-01-16 20:04 ` law at redhat dot com
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=bug-59674-4-KbeTNBcRZC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).