public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "terry.guo at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65710] New: [5 Regression] Thumb1 ICE caused by no register to spill
Date: Thu, 09 Apr 2015 07:03:00 -0000 [thread overview]
Message-ID: <bug-65710-4@http.gcc.gnu.org/bugzilla/> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4180 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65710
Bug ID: 65710
Summary: [5 Regression] Thumb1 ICE caused by no register to
spill
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: terry.guo at arm dot com
Created attachment 35268
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35268&action=edit
test case
Revision 221867 is the fix to PR65647. But it causes another ICE for thumb1
target as below:
$./install/bin/arm-none-eabi-gcc -mthumb -O2 -S regex.i
regex.i: In function âbyte_re_match_2_internalâ:
regex.i:10121:1: error: unable to find a register to spill
}
^
regex.i:10121:1: error: this is the insn:
(insn 12390 15093 12392 2 (set (reg:SI 8731 [8730])
(plus:SI (reg:SI 8731 [8730])
(reg:SI 10838))) regex.i:8483 718 {*thumb1_addsi3}
(expr_list:REG_DEAD (reg:SI 10838)
(nil)))
regex.i:10121:1: internal compiler error: in assign_by_spills, at
lra-assigns.c:1419
0xa36eea _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../src/gcc/gcc/rtl-error.c:110
0x9521e7 assign_by_spills
../../src/gcc/gcc/lra-assigns.c:1419
0x952bd3 lra_assign()
../../src/gcc/gcc/lra-assigns.c:1594
0x94e919 lra(_IO_FILE*)
../../src/gcc/gcc/lra.c:2360
0x90cc09 do_reload
../../src/gcc/gcc/ira.c:5418
0x90cc09 execute
../../src/gcc/gcc/ira.c:5589
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
This issue still happens to the latest trunk.
>From gcc-bugs-return-483070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 09 07:15:21 2015
Return-Path: <gcc-bugs-return-483070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125672 invoked by alias); 9 Apr 2015 07:15:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125650 invoked by uid 48); 9 Apr 2015 07:15:17 -0000
From: "a.vogt at fulguritus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65684] Wrong error message when writing to a string
Date: Thu, 09 Apr 2015 07:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: a.vogt at fulguritus dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-65684-4-ztpxS9Ywp8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg00622.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide684
Alexander Vogt <a.vogt at fulguritus dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #35263|0 |1
is obsolete| |
--- Comment #11 from Alexander Vogt <a.vogt at fulguritus dot com> ---
Created attachment 35269
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id5269&actioníit
Improved wording
next reply other threads:[~2015-04-09 7:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 7:03 terry.guo at arm dot com [this message]
2015-04-09 7:59 ` [Bug target/65710] " rguenth at gcc dot gnu.org
2015-04-09 9:18 ` rguenth at gcc dot gnu.org
2015-04-09 9:30 ` terry.guo at arm dot com
2015-04-09 19:40 ` vmakarov at gcc dot gnu.org
2015-04-09 19:42 ` vmakarov at gcc dot gnu.org
2015-04-10 5:59 ` terry.guo at arm dot com
2015-04-10 6:29 ` jakub at gcc dot gnu.org
2015-04-10 11:30 ` evstupac at gmail dot com
2015-04-10 11:48 ` [Bug target/65710] [4.9 " jakub at gcc dot gnu.org
2015-04-10 13:05 ` yroux at gcc dot gnu.org
2015-04-10 13:06 ` [Bug target/65710] [4.9/5 " jakub at gcc dot gnu.org
2015-04-10 15:25 ` evstupac at gmail dot com
2015-04-10 16:10 ` jakub at gcc dot gnu.org
2015-04-10 16:19 ` vmakarov at gcc dot gnu.org
2015-04-10 16:35 ` jakub at gcc dot gnu.org
2015-04-10 16:38 ` evstupac at gmail dot com
2015-04-10 16:41 ` jakub at gcc dot gnu.org
2015-04-10 16:42 ` vmakarov at gcc dot gnu.org
2015-04-10 16:45 ` jakub at gcc dot gnu.org
2015-04-10 16:47 ` evstupac at gmail dot com
2015-04-10 17:08 ` jakub at gcc dot gnu.org
2015-04-10 18:23 ` yroux at gcc dot gnu.org
2015-04-10 18:53 ` jakub at gcc dot gnu.org
2015-04-10 19:39 ` vmakarov at gcc dot gnu.org
2015-04-10 19:44 ` vmakarov at gcc dot gnu.org
2015-04-10 19:46 ` vmakarov at gcc dot gnu.org
2015-04-10 20:44 ` yroux at gcc dot gnu.org
2015-04-11 7:32 ` jakub at gcc dot gnu.org
2015-04-13 5:22 ` xguo at gcc dot gnu.org
2015-04-13 12:15 ` clyon at gcc dot gnu.org
2015-04-14 3:15 ` terry.guo at arm 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-65710-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).