public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou 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:22:00 -0000 [thread overview]
Message-ID: <bug-64536-4-YBDETuB4ZY@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
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> 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.
Very likely indeed (delete_related_insns does something like that).
next prev parent reply other threads:[~2015-01-08 15:22 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
2015-01-08 15:22 ` ebotcazou at gcc dot gnu.org [this message]
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-YBDETuB4ZY@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).