public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davem at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/55211] [4.8 regression] sparc64-linux bootstrap fails with SIGILL while compiling __mulvti3
Date: Tue, 06 Nov 2012 18:08:00 -0000 [thread overview]
Message-ID: <bug-55211-4-ULkgcsEPdG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55211-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55211
--- Comment #24 from davem at gcc dot gnu.org 2012-11-06 18:07:46 UTC ---
On several occasions, in both public and private emails, I have in fact
expressed my displeasure with how the configure system and the sparc backend
treat things based upon the target triplet.
I've always, and consistently, expressed my position that when configure sees
plain "sparc" gcc should generate 32-bit code by default. And when it sees
"sparc64" it should generate 64-bit code by default. Finally, I've always
stated that there should be an easy way to modify this default (after
installation) on a system wide basis (f.e. via a file under sysroot).
Back to the bug.
I do builds with --with-cpu=niagara4 so that more of the VIS patterns and new
code gets exercised. Among other things, this changes the heuristics for
various things like block moves. This unaligned load is part of a block move
resulting from a structure copy.
In any event, I can reproduce it by using --with-cpu=v8, so I can debug it
properly. I hope to have this fixed by the end of today.
next prev parent reply other threads:[~2012-11-06 18:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 8:28 [Bug bootstrap/55211] New: " mikpe at it dot uu.se
2012-11-05 10:51 ` [Bug bootstrap/55211] " jakub at gcc dot gnu.org
2012-11-05 13:15 ` mikpe at it dot uu.se
2012-11-05 14:12 ` mikpe at it dot uu.se
2012-11-05 16:28 ` jakub at gcc dot gnu.org
2012-11-05 18:11 ` ebotcazou at gcc dot gnu.org
2012-11-05 18:22 ` davem at gcc dot gnu.org
2012-11-05 18:24 ` davem at gcc dot gnu.org
2012-11-05 19:13 ` mikpe at it dot uu.se
2012-11-05 19:16 ` davem at gcc dot gnu.org
2012-11-05 21:38 ` davem at gcc dot gnu.org
2012-11-05 21:41 ` jakub at gcc dot gnu.org
2012-11-05 21:47 ` ebotcazou at gcc dot gnu.org
2012-11-05 21:50 ` davem at gcc dot gnu.org
2012-11-05 21:55 ` ebotcazou at gcc dot gnu.org
2012-11-05 22:04 ` davem at gcc dot gnu.org
2012-11-05 22:08 ` ebotcazou at gcc dot gnu.org
2012-11-05 22:19 ` ebotcazou at gcc dot gnu.org
2012-11-05 22:21 ` davem at gcc dot gnu.org
2012-11-05 22:31 ` ebotcazou at gcc dot gnu.org
2012-11-06 1:44 ` davem at gcc dot gnu.org
2012-11-06 1:44 ` davem at gcc dot gnu.org
2012-11-06 1:49 ` davem at gcc dot gnu.org
2012-11-06 4:15 ` davem at gcc dot gnu.org
2012-11-06 7:50 ` ebotcazou at gcc dot gnu.org
2012-11-06 18:08 ` davem at gcc dot gnu.org [this message]
2012-11-06 22:33 ` davem at gcc dot gnu.org
2012-11-07 7:12 ` davem at gcc dot gnu.org
2012-11-07 7:37 ` ebotcazou at gcc dot gnu.org
2012-11-07 8:42 ` davem at gcc dot gnu.org
2012-11-07 8:45 ` davem 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-55211-4-ULkgcsEPdG@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).