public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marcus at jet dot franken.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66782] Unable to run 64-bit wine after MS->SYSV register changes Date: Tue, 07 Jul 2015 21:42:00 -0000 [thread overview] Message-ID: <bug-66782-4-rT6UsOfQgq@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 --- Comment #3 from marcus at jet dot franken.de --- Created attachment 35927 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35927&action=edit testcase-min.i gcc -S -fPIC -O2 -g testcase.i -o testcase.s there will be a pattern to spot the miscompilation: call strlen@PLT .LVL27: movq 40(%rsp), %rcx movq %rsi, %rdx However %rsi is clobbered by strlen and should not have been used here.
next prev parent reply other threads:[~2015-07-07 21:42 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 [this message] 2015-07-08 8:11 ` [Bug rtl-optimization/66782] [5/6 Regression] " ubizjak at gmail dot com 2015-07-08 11:14 ` 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-rT6UsOfQgq@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: linkBe 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).