public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug rtl-optimization/66665] New: Increment instruction is not propagated into address operand
@ 2015-06-25 13:06 kyukhin at gcc dot gnu.org
  2015-06-30 17:52 ` [Bug rtl-optimization/66665] " hjl.tools at gmail dot com
  2015-06-30 19:11 ` hjl.tools at gmail dot com
  0 siblings, 2 replies; 3+ messages in thread
From: kyukhin at gcc dot gnu.org @ 2015-06-25 13:06 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 66665
           Summary: Increment instruction is not propagated into address
                    operand
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kyukhin at gcc dot gnu.org
  Target Milestone: ---

Hello,

Running this:
make check-gcc RUNTESTFLAGS="CFLAGS='-mregparm=3'
--target_board='unix/-mregparm=3{-m32}' i386.exp=addr-sel-1.c"

If got fail since:
f:
.LFB0:
        movsbl  a+1(%eax), %edx
        incl    %eax            ;; Not propagated ...
        movsbl  b(%eax), %eax   ;; ... to here.
        addl    %edx, %eax
        ret

Increment of %eax is not propagated into load of b.

This kind of propagation is occurred during postreload in `reload_cse_regs',
but increment is promoted to load of a.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug rtl-optimization/66665] Increment instruction is not propagated into address operand
  2015-06-25 13:06 [Bug rtl-optimization/66665] New: Increment instruction is not propagated into address operand kyukhin at gcc dot gnu.org
@ 2015-06-30 17:52 ` hjl.tools at gmail dot com
  2015-06-30 19:11 ` hjl.tools at gmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: hjl.tools at gmail dot com @ 2015-06-30 17:52 UTC (permalink / raw)
  To: gcc-bugs

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-06-30
     Ever confirmed|0                           |1

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
It is caused by the combination of -mregparm=3 -mtune=i686.
-mregparm=3 -mtune=generic -O2 gives

f:
        .cfi_startproc
        movsbl  a+1(%eax), %edx
        movsbl  b+1(%eax), %eax
        addl    %edx, %eax
        ret
        .cfi_endproc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug rtl-optimization/66665] Increment instruction is not propagated into address operand
  2015-06-25 13:06 [Bug rtl-optimization/66665] New: Increment instruction is not propagated into address operand kyukhin at gcc dot gnu.org
  2015-06-30 17:52 ` [Bug rtl-optimization/66665] " hjl.tools at gmail dot com
@ 2015-06-30 19:11 ` hjl.tools at gmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: hjl.tools at gmail dot com @ 2015-06-30 19:11 UTC (permalink / raw)
  To: gcc-bugs

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |6.0


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-06-30 19:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-25 13:06 [Bug rtl-optimization/66665] New: Increment instruction is not propagated into address operand kyukhin at gcc dot gnu.org
2015-06-30 17:52 ` [Bug rtl-optimization/66665] " hjl.tools at gmail dot com
2015-06-30 19:11 ` hjl.tools at gmail dot com

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).