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 rtl-optimization/64536] [4.9/5 Regression] Undefined .L* symbol starting with jump2 on s390x
Date: Thu, 08 Jan 2015 15:12:00 -0000	[thread overview]
Message-ID: <bug-64536-4-uH4upTvRj8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64536-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, we have bb 6:
(note 180 23 24 6 [bb 6] NOTE_INSN_BASIC_BLOCK)
(insn 24 180 25 6 (set (reg:DI 1 %r1 [orig:88 b ] [88])
        (zero_extend:DI (reg:SI 1 %r1 [orig:85 b+4 ] [85]))) method-to-ir3.i:15
184 {*zero_extendsidi2}
     (nil))
(insn 25 24 289 6 (set (reg:DI 1 %r1 [orig:88 b ] [88])
        (ashift:DI (reg:DI 1 %r1 [orig:88 b ] [88])
            (const_int 3 [0x3]))) method-to-ir3.i:15 570 {*ashldi3}
     (nil))
(insn 289 25 27 6 (set (reg/f:DI 2 %r2 [158])
        (mem/c:DI (plus:DI (reg/f:DI 15 %r15)
                (const_int 184 [0xb8])) [5 %sfp+-8 S8 A64])) method-to-ir3.i:15
63 {*movdi_64}
     (nil))
(insn 27 289 28 6 (set (reg:DI 1 %r1 [87])
        (mem/u/c:DI (plus:DI (reg/f:DI 2 %r2 [158])
                (reg:DI 1 %r1 [orig:88 b ] [88])) [0  S8 A8]))
method-to-ir3.i:15 63 {*movdi_64}
     (expr_list:REG_EQUAL (mem/u/c:DI (plus:DI (reg:DI 1 %r1 [orig:88 b ] [88])
                (label_ref:DI 29)) [0  S8 A8])
        (nil)))
(jump_insn 28 27 29 6 (parallel [
            (set (pc)
                (plus:DI (reg/f:DI 2 %r2 [158])
                    (reg:DI 1 %r1 [87])))
            (use (label_ref 29))
        ]) method-to-ir3.i:15 626 {casesi_jump}
     (expr_list:REG_DEAD (reg/f:DI 2 %r2 [158])
        (expr_list:REG_DEAD (reg:DI 1 %r1 [87])
            (nil)))
 -> 29)
with:
(code_label 29 28 30 7 "" [2 uses])
(jump_table_data 30 29 31 (addr_diff_vec:DI (label_ref:DI 29)
         [
            (label_ref:DI 50)
            (label_ref:DI 50)
            (label_ref:DI 50)
            (label_ref:DI 50)
        ]
        (const_int 0 [0])
        (const_int 0 [0])))
after it (outside of bb) (as all the case labels do the same thing, they have
been jump threaded, but unfortunately not at GIMPLE, but only at RTL level) and
post_order_compute calls tidy_fallthru_edges which calls tidy_fallthru_edge
on the only successor edge from bb 6 (6 -> 9, bb 9 is the bb starting with
code_label 50).  When all the jump_table_data labels point to the same
destination, it is reasonable to optimize that to direct jump, but I guess we
need to take care about making sure that the code_label before the
jump_table_data is only removed when it has zero LABEL_NUSES.


  parent reply	other threads:[~2015-01-08 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 10:05 [Bug rtl-optimization/64536] New: " jakub at gcc dot gnu.org
2015-01-08 10:06 ` [Bug rtl-optimization/64536] " jakub at gcc dot gnu.org
2015-01-08 15:12 ` jakub at gcc dot gnu.org [this message]
2015-01-08 15:22 ` ebotcazou at gcc dot gnu.org
2015-01-08 16:46 ` jakub at gcc dot gnu.org
2015-01-09 21:17 ` jakub at gcc dot gnu.org
2015-01-09 21:36 ` jakub at gcc dot gnu.org
2015-01-09 22:15 ` 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-64536-4-uH4upTvRj8@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).