public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/70164] [8/9/10 Regression] Code/performance regression due to poor register allocation on Cortex-M0
Date: Fri, 10 Apr 2020 10:57:40 +0000	[thread overview]
Message-ID: <bug-70164-4-UB7ol6jLJ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-70164-4@http.gcc.gnu.org/bugzilla/>

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

Christophe Lyon <clyon at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clyon at gcc dot gnu.org

--- Comment #24 from Christophe Lyon <clyon at gcc dot gnu.org> ---
With today's trunk, I still see the same problem:

history_expand_line_internal:
        @ args = 0, pretend = 0, frame = 8
        @ frame_needed = 0, uses_anonymous_args = 0
        push    {r0, r1, r2, r4, r5, r6, r7, lr}
        ldr     r3, .L3
        ldr     r6, .L3+4
        ldr     r7, [r3]
        ldr     r3, [r6]       ; ; <--- load of 'hist_verify' onto r3
        movs    r5, r0
        str     r3, [sp, #4]    ; <--- Spill
        movs    r3, #0
        str     r3, [r6]            
        bl      pre_process_line
        ldr     r3, [sp, #4]    ; <--- reload
        movs    r4, r0
        adds    r7, r7, r3
        str     r7, [r6]
        cmp     r5, r0
        bne     .L1
        bl      str_len
        adds    r0, r0, #1
        bl      x_malloc
        movs    r1, r4
        bl      str_cpy
        movs    r4, r0
.L1:
        @ sp needed
        movs    r0, r4
        pop     {r1, r2, r3, r4, r5, r6, r7, pc}
.L4:
        .align  2
.L3:
        .word   a1
        .word   hist_verify

       reply	other threads:[~2020-04-10 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-70164-4@http.gcc.gnu.org/bugzilla/>
2020-04-10 10:57 ` clyon at gcc dot gnu.org [this message]
2020-04-21 15:20 ` vmakarov at gcc dot gnu.org
2020-04-21 16:14 ` clyon at gcc dot gnu.org
2020-04-21 19:03 ` vmakarov at gcc dot gnu.org
2021-05-14  9:48 ` [Bug rtl-optimization/70164] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:07 ` rguenth at gcc dot gnu.org
2022-05-27  9:36 ` [Bug rtl-optimization/70164] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:32 ` jakub at gcc dot gnu.org
2023-07-07 10:31 ` [Bug rtl-optimization/70164] [11/12/13/14 " rguenth 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-70164-4-UB7ol6jLJ3@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).