public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62025] [4.9/4.10 Regression] Miscompilation of openssl sha512.c
Date: Tue, 12 Aug 2014 11:06:00 -0000	[thread overview]
Message-ID: <bug-62025-4-JVMAAgwdG1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62025-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62025

--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Just verified the trunk and it is the same thing there, also sched2 generating:
        al      %r3,252(%r8)
        ahi     %r8,128
        alc     %r2,120(%r8)
where the first insn is cc setter, second cc clobber and third cc user and
clobber, so the r8=r8+128 insn should not have been scheduled in between those
two.  It seems scheduler has some code to adjust the address (248 -> 120) based
on the r8 adjustment, otherwise it would be wrong to move it even because of r8
register, perhaps if we take that path we don't fully check other side effects
(cc clobber in this case).  s390 AFAIK doesn't have addition which doesn't
clobber flags, unlike many other architectures.


  parent reply	other threads:[~2014-08-12 11:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-62025-4@http.gcc.gnu.org/bugzilla/>
2014-08-05 14:58 ` jakub at gcc dot gnu.org
2014-08-05 15:02 ` jakub at gcc dot gnu.org
2014-08-11 14:02 ` jakub at gcc dot gnu.org
2014-08-11 16:47 ` jakub at gcc dot gnu.org
2014-08-12  4:07 ` law at redhat dot com
2014-08-12  6:52 ` amker at gcc dot gnu.org
2014-08-12  6:53 ` law at redhat dot com
2014-08-12  8:17 ` jakub at gcc dot gnu.org
2014-08-12  8:55 ` jakub at gcc dot gnu.org
2014-08-12  9:57 ` jakub at gcc dot gnu.org
2014-08-12 10:38 ` amker at gcc dot gnu.org
2014-08-12 11:06 ` jakub at gcc dot gnu.org [this message]
2014-08-12 11:47 ` jakub at gcc dot gnu.org
2014-08-12 12:17 ` jakub at gcc dot gnu.org
2014-08-12 14:30 ` law at redhat dot com
2014-08-12 21:25 ` jakub at gcc dot gnu.org
2014-08-12 22:04 ` jakub at gcc dot gnu.org
2014-08-13  4:22 ` amker.cheng at gmail dot com
2014-08-13 16:25 ` [Bug target/62025] [4.9/5 " jakub at gcc dot gnu.org
2014-08-13 16:27 ` jakub at gcc dot gnu.org
2014-09-01 11:16 ` jakub at gcc dot gnu.org
2014-09-01 11:50 ` jakub at gcc dot gnu.org
2014-10-14 14:01 ` 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-62025-4-JVMAAgwdG1@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).