public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59674] On m68k and vax variables stack variables with > MAX_STACK_ALIGNMENT make ssp fail
Date: Thu, 23 Jan 2014 17:12:00 -0000 [thread overview]
Message-ID: <bug-59674-4-erITDC38iY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59674-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59674
Martin Husemann <martin at netbsd dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin at netbsd dot org
--- Comment #8 from Martin Husemann <martin at netbsd dot org> ---
(In reply to Andreas Schwab from comment #7)
> If you have fundamental types with stricter alignment requirements than
> provided by STACK_BOUNDARY your ABI has a problem, and this SSP failure is
> just one symptom.
Why is that a fundamental problem? It is not that different to i386 and data
used for MMX/SSE instructions - "not nice", but the compiler should be able to
cope.
next prev parent reply other threads:[~2014-01-23 17:12 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 [this message]
2014-01-24 21:37 ` [Bug target/59674] " schwab@linux-m68k.org
2015-01-16 18:56 ` law at redhat dot com
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-erITDC38iY@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).