public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47766] New: [x32] -fstack-protector doesn't work
Date: Wed, 16 Feb 2011 13:50:00 -0000 [thread overview]
Message-ID: <bug-47766-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47766
Summary: [x32] -fstack-protector doesn't work
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
[hjl@gnu-6 ilp32-22]$ cat x.c
int
parse_opt (int key)
{
struct
{
int arg[key];
} reqdata;
return 0;
}
[hjl@gnu-6 ilp32-22]$ make x.s
/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/ -S -o x.s -mx32 -O2 -g
-fstack-protector x.c
x.c: In function \u2018parse_opt\u2019:
x.c:9:1: error: unrecognizable insn:
(insn 4 3 6 2 (parallel [
(set (mem/v/f/c/i:SI (plus:DI (reg/f:DI 54 virtual-stack-vars)
(const_int -4 [0xfffffffffffffffc])) [2 D.2703+0 S4
A32])
(unspec:DI [
(const_int 40 [0x28])
] UNSPEC_SP_TLS_SET))
(set (scratch:DI)
(const_int 0 [0]))
(clobber (reg:CC 17 flags))
]) x.c:3 -1
(nil))
x.c:9:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [x.s] Error 1
[hjl@gnu-6 ilp32-22]$
next reply other threads:[~2011-02-16 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 13:50 hjl.tools at gmail dot com [this message]
2011-02-16 20:45 ` [Bug target/47766] " hjl at gcc dot gnu.org
2011-08-01 18:22 ` hjl at gcc dot gnu.org
2011-08-01 18:23 ` hjl.tools at gmail dot com
2011-08-02 9:02 ` uros at gcc dot gnu.org
2011-08-06 14:26 ` hjl 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-47766-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).