public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enkovich.gnu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64317] [5 Regression] Ineffective allocation of PIC base register
Date: Thu, 05 Feb 2015 12:22:00 -0000	[thread overview]
Message-ID: <bug-64317-4-r35h3Dbooz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64317-4@http.gcc.gnu.org/bugzilla/>

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

Ilya Enkovich <enkovich.gnu at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |enkovich.gnu at gmail dot com

--- Comment #3 from Ilya Enkovich <enkovich.gnu at gmail dot com> ---
Created attachment 34675
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34675&action=edit
Another reproducer

I found one more reproducer for the problem.  Generated code for multiple
'output' calls inlined into test':

..
.L5:
        movl    28(%esp), %edx               <-- load PIC reg
        movl    %edi, (%ecx)
        leal    (%ebx,%eax), %ecx
        cmpl    %ecx, %ebp
        movl    %ebx, out_pos@GOTOFF(%edx)
        movl    val3@GOTOFF(%edx), %edi
        jnb     .L6
        movl    28(%esp), %ebx              <-- have value in EDX
        movl    out@GOTOFF(%ebx), %ebx
        leal    (%ebx,%eax), %ecx
.L6:
        movl    28(%esp), %edx              <-- NOP
        movl    %edi, (%ebx)
        leal    (%ecx,%eax), %ebx
        cmpl    %ebx, %ebp
        movl    %ecx, out_pos@GOTOFF(%edx)
        movl    val4@GOTOFF(%edx), %edi
        jnb     .L7
        movl    28(%esp), %ecx             <-- have value in EDX
        movl    out@GOTOFF(%ecx), %ecx
        leal    (%ecx,%eax), %ebx
.L7:
        movl    28(%esp), %edx             <-- NOP
        movl    %edi, (%ecx)
...

BTW if I put __attribute__((noinline)) for crc32 function then mentioned code
becomes better and we don't have these two useless instructions in each
function instance.

Compilation string:

gcc -Ofast -funroll-loops -m32 -march=slm -fPIE test.i -S

Used compiler:

gcc version 5.0.0 20150203 (experimental) (GCC)


  parent reply	other threads:[~2015-02-05 12:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 15:03 [Bug rtl-optimization/64317] New: " izamyatin at gmail dot com
2014-12-15 15:07 ` [Bug rtl-optimization/64317] " rguenth at gcc dot gnu.org
2015-01-13 10:26 ` rguenth at gcc dot gnu.org
2015-01-23 20:17 ` vmakarov at gcc dot gnu.org
2015-02-05 12:22 ` enkovich.gnu at gmail dot com [this message]
2015-02-06  9:52 ` jakub at gcc dot gnu.org
2015-02-06 10:06 ` enkovich.gnu at gmail dot com
2015-02-10 22:17 ` vmakarov at gcc dot gnu.org
2015-02-12 21:04 ` law at redhat dot com
2015-02-13  3:35 ` vmakarov at gcc dot gnu.org
2015-02-13  3:37 ` vmakarov at gcc dot gnu.org
2015-02-13  8:06 ` enkovich.gnu at gmail dot com
2015-02-19 13:18 ` law at redhat dot com
2015-02-19 16:21 ` vmakarov at gcc dot gnu.org
2015-02-20 23:24 ` law at redhat dot com
2015-02-21 20:10 ` vmakarov at gcc dot gnu.org
2015-02-27 23:07 ` vmakarov at gcc dot gnu.org
2015-03-03 19:08 ` law at redhat dot com
2015-03-03 22:39 ` law at redhat dot com
2015-03-04 17:39 ` law at redhat dot com
2015-03-05 15:37 ` vmakarov at gcc dot gnu.org
2015-03-05 20:01 ` law at redhat dot com
2015-03-09 17:12 ` law at redhat dot com
2015-03-23  7:53 ` law at gcc dot gnu.org
2015-03-23  7:54 ` law at redhat 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-64317-4-r35h3Dbooz@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).