public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/66782] [5/6 Regression] Unable to run 64-bit wine after MS->SYSV register changes
Date: Wed, 08 Jul 2015 08:11:00 -0000 [thread overview]
Message-ID: <bug-66782-4-CqtBcEw0iO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66782-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66782
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Version|5.1.0 |6.0
Keywords| |ra
Last reconfirmed| |2015-07-08
Component|target |rtl-optimization
CC| |ubizjak at gmail dot com,
| |vmakarov at gcc dot gnu.org
Ever confirmed|0 |1
Summary|Unable to run 64-bit wine |[5/6 Regression] Unable to
|after MS->SYSV register |run 64-bit wine after
|changes |MS->SYSV register changes
Target Milestone|--- |5.2
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
When compiled with "-O2 -fPIC", we have following sequence in _.ira dump:
...
211: r225:DI=[frame:DI-0x80]
REG_EQUIV [frame:DI-0x80]
212: {r224:DI=r225:DI-r89:DI;clobber flags:CC;}
REG_DEAD r225:DI
REG_UNUSED flags:CC
REG_EQUAL [frame:DI-0x80]-r89:DI
213: [r111:DI+r224:DI]=0x36646d61
214: [r111:DI+r224:DI+0x4]=0x34
REG_DEAD r224:DI
215: r121:DI=[frame:DI-0x80]
216: di:DI=r111:DI
217: ax:DI=call [`strlen'] argc:0
REG_DEAD di:DI
REG_CALL_DECL `strlen'
REG_EH_REGION 0
218: r227:DI=ax:DI
REG_DEAD ax:DI
221: {r229:DI=r111:DI+r227:DI;clobber flags:CC;}
REG_DEAD r227:DI
REG_UNUSED flags:CC
222: {r230:DI=r89:DI-r121:DI;clobber flags:CC;}
REG_UNUSED flags:CC
...
and following in _.reload dump:
...
211: NOTE_INSN_DELETED
591: di:DI=[sp:DI+0x70]
633: si:DI=[sp:DI+0x18]
593: dx:DI=si:DI
212: {di:DI=di:DI-dx:DI;clobber flags:CC;}
REG_EQUAL [frame:DI-0x80]-r89:DI
592: ax:DI=di:DI
213: [bp:DI+ax:DI]=0x36646d61
214: [bp:DI+ax:DI+0x4]=0x34
215: cx:DI=[sp:DI+0x70]
631: [sp:DI+0x28]=cx:DI
216: di:DI=bp:DI
217: ax:DI=call [`strlen'] argc:0
REG_CALL_DECL `strlen'
REG_EH_REGION 0
218: ax:DI=ax:DI
221: {di:DI=bp:DI+ax:DI;clobber flags:CC;}
594: dx:DI=si:DI
632: cx:DI=[sp:DI+0x28]
222: {dx:DI=dx:DI-cx:DI;clobber flags:CC;}
...
Please note (insn 594) that uses clobbered SI register, although the call insn
clobbers it:
(call_insn/i 217 216 218 25 (set (reg:DI 0 ax)
(call (mem:QI (symbol_ref:DI ("strlen") [flags 0x41] <function_decl
0x2b7e7ae707e0 strlen>) [0 __builtin_strlen S1 A8])
(const_int 0 [0]))) pr66782.i:96 656 {*call_value}
(expr_list:REG_CALL_DECL (symbol_ref:DI ("strlen") [flags 0x41]
<function_decl 0x2b7e7ae707e0 strlen>)
(expr_list:REG_EH_REGION (const_int 0 [0])
(nil)))
(expr_list (clobber (reg:TI 52 xmm15))
(expr_list (clobber (reg:TI 51 xmm14))
(expr_list (clobber (reg:TI 50 xmm13))
(expr_list (clobber (reg:TI 49 xmm12))
(expr_list (clobber (reg:TI 48 xmm11))
(expr_list (clobber (reg:TI 47 xmm10))
(expr_list (clobber (reg:TI 46 xmm9))
(expr_list (clobber (reg:TI 45 xmm8))
(expr_list (clobber (reg:TI 28 xmm7))
(expr_list (clobber (reg:TI 27 xmm6))
(expr_list (clobber (reg:DI 5 di))
(expr_list (clobber (reg:DI 4
si))
(expr_list:DI (use (reg:DI
5 di))
(nil)))))))))))))))
Confirmed with latest 6.0 mainline [trunk revision 225533] as RA problem.
CC RA expert.
>From gcc-bugs-return-491715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 08 08:26:55 2015
Return-Path: <gcc-bugs-return-491715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107246 invoked by alias); 8 Jul 2015 08:26:53 -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 107212 invoked by uid 48); 8 Jul 2015 08:26:49 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/66802] New: Some of the Bugzilla Bug fields descriptions do not reflect GCC development
Date: Wed, 08 Jul 2015 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-66802-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-07/txt/msg00605.txt.bz2
Content-length: 827
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf802
Bug ID: 66802
Summary: Some of the Bugzilla Bug fields descriptions do not
reflect GCC development
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: ubizjak at gmail dot com
Target Milestone: ---
Some of the "Bug Fields" descriptions [1] do not reflect reality. STATUS and
RESOLUTION descriptions are not correct.
IMO, Priority and Severity fields also need a better description - at least the
criteria for Priority and Severity selections, and who can set these fields
(Release Managers?).
[1] https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html
next prev parent reply other threads:[~2015-07-08 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:15 [Bug c/66782] New: " austinenglish at gmail dot com
2015-07-06 18:53 ` [Bug c/66782] " ubizjak at gmail dot com
2015-07-06 19:54 ` [Bug target/66782] " ubizjak at gmail dot com
2015-07-07 21:42 ` marcus at jet dot franken.de
2015-07-08 8:11 ` ubizjak at gmail dot com [this message]
2015-07-08 11:14 ` [Bug rtl-optimization/66782] [5/6 Regression] " ubizjak at gmail dot com
2015-07-08 11:48 ` matz at gcc dot gnu.org
2015-07-08 19:36 ` vmakarov at gcc dot gnu.org
2015-07-08 19:43 ` vmakarov at gcc dot gnu.org
2015-07-09 2:28 ` hjl.tools at gmail dot com
2015-07-09 15:40 ` vmakarov at gcc dot gnu.org
2015-07-10 13:17 ` vmakarov at gcc dot gnu.org
2015-07-10 13:48 ` trippels at gcc dot gnu.org
2015-07-12 10:18 ` marcus at jet dot franken.de
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-66782-4-CqtBcEw0iO@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).