public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "christos at zoulas dot com" <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: Sat, 04 Jan 2014 21:21:00 -0000 [thread overview] Message-ID: <bug-59674-4-8x54EHVjk6@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 --- Comment #6 from Christos Zoulas <christos at zoulas dot com> --- On Jan 4, 8:42pm, gcc-bugzilla@gcc.gnu.org ("mikpelinux at gmail dot com") wrote: -- Subject: [Bug c/59674] On m68k and vax variables stack variables with > MA | That is correct, m68k-linux has looser alignment rules than most other archs. | Which is why I also tested vax-linux, hoping that its ABI would be more in line | with other VAX targets. We have the same problem with sh3 also. I think that the VAX issue is a bit different. I will test and provide more details for both platforms. christos
next prev parent reply other threads:[~2014-01-04 21:21 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 [this message] 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 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-8x54EHVjk6@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: linkBe 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).