From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: How to configure a bi-arch PowerPC GCC?
Date: Fri, 20 Jan 2017 07:35:00 -0000 [thread overview]
Message-ID: <5881BDB2.3050505@embedded-brains.de> (raw)
In-Reply-To: <20170120010404.GW30284@gate.crashing.org>
Hello Segher,
On 20/01/17 02:04, Segher Boessenkool wrote:
> Hi,
>
> On Thu, Jan 19, 2017 at 01:41:33PM +0100, Sebastian Huber wrote:
>> conftest.c:16:1: error: unrecognizable insn:
>> }
>> ^
>> (insn/f 22 21 23 2 (parallel [
>> (set (reg/f:DI 1 1)
>> (plus:SI (reg/f:DI 1 1)
>> (const_int 16 [0x10])))
>> (set (mem:BLK (reg/f:DI 1 1) [0 A8])
>> (const_int 0 [0]))
>> (set (mem:BLK (reg/f:DI 1 1) [0 A8])
>> (const_int 0 [0]))
>> ]) "conftest.c":16 -1
>> (expr_list:REG_CFA_DEF_CFA (reg/f:DI 1 1)
>> (nil)))
> This is stack_restore_tie, which requires TARGET_32BIT.
>
> It currently is only generated from rs6000_emit_stack_reset:
>
> /* This blockage is needed so that sched doesn't decide to move
> the sp change before the register restores. */
> if (DEFAULT_ABI == ABI_V4
> || (TARGET_SPE_ABI
> && info->spe_64bit_regs_used != 0
> && info->first_gp_reg_save != 32))
> return emit_insn (gen_stack_restore_tie (updt_reg_rtx, frame_reg_rtx,
> GEN_INT (frame_off)));
>
> so you seem to have 64-bit ABI_V4? I wonder how well tested that is,
> you are likely to run into more problems. Either stack_restore_tie or
> the above code will need a tweak.
thanks for your help. I would had a hard time to figure this out myself.
I am flexible in terms of the ABI choice for the 64-bit PowerPC. I guess
the ABI_ELFv2 is the way to go?
I had to provide SUBSUBTARGET_OVERRIDE_OPTIONS in rtems.h (in
config/rs6000/) to set the ABI. The sysv4.h doesn't care about
-mabi=elfv2. There seems to be some copy and paste in linux64.h and
freebsd64.h for their SUBSUBTARGET_OVERRIDE_OPTIONS. Maybe the common
stuff should move to sysv4.h?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2017-01-20 7:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 12:41 Sebastian Huber
2017-01-20 1:04 ` Segher Boessenkool
2017-01-20 7:35 ` Sebastian Huber [this message]
2017-01-21 0:46 ` Segher Boessenkool
2017-01-23 8:19 ` Sebastian Huber
2017-01-23 17:18 ` Segher Boessenkool
2017-01-25 12:14 ` Sebastian Huber
[not found] ` <58889605.4060501@embedded-brains.de>
2017-01-25 17:55 ` Segher Boessenkool
2017-01-30 10:38 ` Sebastian Huber
2017-01-30 12:13 ` Sebastian Huber
2017-01-31 5:57 ` Segher Boessenkool
2017-01-31 8:16 ` Segher Boessenkool
2017-07-20 22:40 ` Sebastian Huber
2017-07-23 13:16 ` Segher Boessenkool
2017-09-13 13:11 ` Andreas Schwab
2017-09-14 11:50 ` Sebastian Huber
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=5881BDB2.3050505@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc@gcc.gnu.org \
--cc=segher@kernel.crashing.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).