public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50091] New: [4.5/4.6/4.7 Regression] -fstack-check gives bad assembly on powerpc-apple-darwin9
Date: Mon, 15 Aug 2011 15:26:00 -0000 [thread overview]
Message-ID: <bug-50091-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50091
Bug #: 50091
Summary: [4.5/4.6/4.7 Regression] -fstack-check gives bad
assembly on powerpc-apple-darwin9
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dominiq@lps.ens.fr
CC: iains@gcc.gnu.org, spop@gcc.gnu.org
Host: powerpc-apple-darwin9
Target: powerpc-apple-darwin9
Build: powerpc-apple-darwin9
On powerpc-apple-darwin9 I get
FAIL: gcc.dg/graphite/run-id-pr47653.c (test for excess errors)
The error is
[karma] f90/bug% gcc47 -O -fstack-check=generic -ftree-pre -fgraphite-identity
/opt/gcc/work/gcc/testsuite/gcc.dg/graphite/run-id-pr47653.c
/var/tmp//ccQC61mg.s:12:Parameter syntax error (parameter 1)
/var/tmp//ccQC61mg.s:13:Parameter syntax error (parameter 1)
The syntax error comming from "stw 0,..." in
...
stw 0,-12284(r1)
mr r0,r1
stw 0,-12556(r1)
...
It turns out that -fstack-check=generic (or -fstack-check) is enough to trigger
the error for gcc 4.5.3, 4.6.1, and trunk, but not for 4.4.6. I have tested
some C files and this seems quite generic although
gcc/testsuite/gcc.dg/pr48134.c assembles with -O or -O1, but not with -O2.
QUESTION for graphite: is -fstack-check=generic really necessary for
gcc.dg/graphite/run-id-pr47653.c?
next reply other threads:[~2011-08-15 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 15:26 dominiq at lps dot ens.fr [this message]
2011-08-16 8:42 ` [Bug target/50091] " rguenth at gcc dot gnu.org
2011-08-16 17:23 ` ebotcazou at gcc dot gnu.org
2011-08-16 17:28 ` pinskia at gmail dot com
2011-08-17 22:39 ` dominiq at lps dot ens.fr
2011-08-20 14:22 ` iains at gcc dot gnu.org
2011-08-20 14:52 ` schwab@linux-m68k.org
2011-09-03 13:29 ` ebotcazou at gcc dot gnu.org
2011-09-03 14:20 ` iains at gcc dot gnu.org
2011-09-03 14:45 ` ebotcazou at gcc dot gnu.org
2011-09-03 14:46 ` ebotcazou at gcc dot gnu.org
2011-09-03 16:48 ` iains at gcc dot gnu.org
2011-09-03 17:29 ` ebotcazou at gcc dot gnu.org
2011-09-04 11:19 ` iains at gcc dot gnu.org
2011-09-04 13:02 ` ebotcazou at gcc dot gnu.org
2011-09-04 15:29 ` iains at gcc dot gnu.org
2011-09-18 22:04 ` [Bug target/50091] [4.5/4.6/4.7 Regression] -fstack-check generates wrong assembly ebotcazou at gcc dot gnu.org
2011-09-18 22:05 ` ebotcazou at gcc dot gnu.org
2011-09-18 22:33 ` ebotcazou at gcc dot gnu.org
2011-09-18 23:32 ` ebotcazou at gcc dot gnu.org
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-50091-4@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).