public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/65805] [5/6 Regression] Chromium gets miscompiled
Date: Sun, 19 Apr 2015 18:27:00 -0000 [thread overview]
Message-ID: <bug-65805-4-HuYVwEuAHE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65805-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65805
--- Comment #4 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Markus Trippelsdorf from comment #3)
> It is clearer to see the issue if one compiles the whole file with
> -fno-lra-remat:
>
> markus@x4 Release % g++ -S -fno-lra-remat -fPIC -fvisibility=hidden -pthread
> -march=x86-64 -O2 -fno-exceptions -fno-rtti -std=gnu++11 -Wall -c
> file_util.ii -o out_good
> markus@x4 Release % g++ -S -fPIC -fvisibility=hidden -pthread -march=x86-64
> -O2 -fno-exceptions -fno-rtti -std=gnu++11 -Wall -c file_util.ii -o out_bad
> markus@x4 Release % diff -u out_good out_bad
> ...
> @@ -4616,7 +4616,7 @@
> pushq %rbp
> .cfi_def_cfa_offset 128
> movl 20(%rsp), %edx
> - movq 24(%rsp), %rdi
> + leaq 64(%rsp), %rdi
> call
> _ZN10extensions9Extension6CreateERKN4base8FilePathENS_8Manifest8LocationERKNS
> 1_15DictionaryValueEiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPS
> F_@PLT
> movq 32(%rsp), %r13
> popq %rax
>
> When I change "leaq 64(%rsp), %rdi" back to "movq 24(%rsp), %rdi"
> chromium runs fine.
Thanks. I reproduced the bug and started to work on it. The problem is in
rematerialization when FP-SP offset is different at points of original insn and
rematerialized insn. I hope the patch will be ready tomorrow.
next prev parent reply other threads:[~2015-04-19 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 7:50 [Bug tree-optimization/65805] New: " trippels at gcc dot gnu.org
2015-04-19 10:20 ` [Bug rtl-optimization/65805] " trippels at gcc dot gnu.org
2015-04-19 10:52 ` trippels at gcc dot gnu.org
2015-04-19 17:39 ` trippels at gcc dot gnu.org
2015-04-19 18:27 ` vmakarov at gcc dot gnu.org [this message]
2015-04-19 23:49 ` vmakarov at gcc dot gnu.org
2015-04-20 8:22 ` [Bug rtl-optimization/65805] [5 " rguenth at gcc dot gnu.org
2015-04-23 19:08 ` vmakarov at gcc dot gnu.org
2015-04-24 9:13 ` jakub 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-65805-4-HuYVwEuAHE@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).