public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: gcc-patches@gcc.gnu.org, Mikhail Maltsev <maltsevm@gmail.com>,
	rdsandiford@googlemail.com
Subject: Re: Add .def file for public target instructions
Date: Fri, 26 Jun 2015 07:42:00 -0000	[thread overview]
Message-ID: <20150626070647.GA402@x4> (raw)
In-Reply-To: <87ioaegtcp.fsf@googlemail.com>

On 2015.06.23 at 19:41 +0100, Richard Sandiford wrote:
> 
> gcc/
> 	* Makefile.in (TARGET_DEF): Add target-insns.def.
> 	(.PRECIOUS, simple_rtl_generated_h): Add insn-target-def.h.
> 	(build/gentarget-def.o): New rule.
> 	(genprogrtl): Add target-def.
> 	* target-insns.def, gentarget-def.c: New files.
> 	* target.def: Add targetm.have_* and targetm.gen_* hooks,
> 	based on the contents of target-insns.def.
> 	* defaults.h (HAVE_simple_return, gen_simple_return): Delete.
> 	(HAVE_return, gen_return): Delete.
> 	* target-def.h: Include insn-target-def.h.
> 	* cfgrtl.c (force_nonfallthru_and_redirect): Use targetm interface
> 	instead of direct calls.  Rely on them to do the appropriate assertions.
> 	* function.c (gen_return_pattern): Likewise.  Return an rtx_insn *.
> 	(convert_jumps_to_returns): Use targetm interface instead of
> 	direct calls.
> 	(thread_prologue_and_epilogue_insns): Likewise.
> 	* reorg.c (find_end_label, dbr_schedule): Likewise.
> 	* shrink-wrap.h (SHRINK_WRAPPING_ENABLED): Likewise.
> 	* shrink-wrap.c (convert_to_simple_return): Likewise.
> 	(try_shrink_wrapping): Use SHRINK_WRAPPING_ENABLED.

The patch breaks bootstrap on ppc64le. During libgcc configuration:

conftest.c: In function 'main':
conftest.c:16:1: internal compiler error: in as_a, at is-a.h:192
 }
 ^
0x1010411b as_a<rtx_jump_insn*, rtx_insn>
        ../../gcc/gcc/is-a.h:192
0x1040ccd3 as_a<rtx_jump_insn*, rtx_insn>
        ../../gcc/gcc/emit-rtl.c:4750
0x1040ccd3 emit_jump_insn_after(rtx_def*, rtx_def*)
        ../../gcc/gcc/emit-rtl.c:4749
0x104c378f emit_return_into_block(bool, basic_block_def*)
        ../../gcc/gcc/function.c:5633
0x104c3ee7 emit_return_for_exit(edge_def*, bool)
        ../../gcc/gcc/function.c:5779
0x104c9ee3 thread_prologue_and_epilogue_insns()
        ../../gcc/gcc/function.c:5961
0x104ca39f rest_of_handle_thread_prologue_and_epilogue
        ../../gcc/gcc/function.c:6443
0x104ca39f execute
        ../../gcc/gcc/function.c:6481
Please submit a full bug report,
with preprocessed source if appropriate.



-- 
Markus

  parent reply	other threads:[~2015-06-26  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 18:42 Richard Sandiford
2015-06-24  6:36 ` Jeff Law
2015-06-25 20:11 ` H.J. Lu
2015-06-25 23:00   ` H.J. Lu
2015-06-25 23:37     ` Andrew Pinski
2015-06-25 23:55       ` H.J. Lu
2015-06-26  6:33         ` H.J. Lu
2015-06-26  8:50           ` Richard Sandiford
2015-06-26  7:42 ` Markus Trippelsdorf [this message]
2015-06-26  8:45   ` Richard Sandiford
2015-06-26 10:15     ` Richard Sandiford
2015-07-01  9:39 ` Trevor Saunders
2015-07-01  9:53   ` Richard Biener
2015-07-01 10:14     ` Richard Sandiford
2015-07-01 10:18       ` Richard Sandiford

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=20150626070647.GA402@x4 \
    --to=markus@trippelsdorf.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=maltsevm@gmail.com \
    --cc=rdsandiford@googlemail.com \
    /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).