From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [PowerPC/RTEMS] Add 64-bit support using ELFv2 ABI
Date: Thu, 27 Jul 2017 05:28:00 -0000 [thread overview]
Message-ID: <4518ab10-1391-5d3b-4b7e-af1e502d0919@embedded-brains.de> (raw)
In-Reply-To: <20170726175619.GP13471@gate.crashing.org>
On 26/07/17 19:56, Segher Boessenkool wrote:
> On Tue, Jul 25, 2017 at 02:25:21PM +0200, Sebastian Huber wrote:
>> Add 64-bit support for RTEMS using the ELFv2 ABI with 64-bit long
>> double.
>>
>> diff --git a/gcc/config.gcc b/gcc/config.gcc
>> index 2ae0218b5fc..aab7f65c1df 100644
>> --- a/gcc/config.gcc
>> +++ b/gcc/config.gcc
>> @@ -2424,7 +2424,7 @@ powerpc-*-rtems*spe*)
>> tmake_file="${tmake_file} powerpcspe/t-fprules powerpcspe/t-rtems powerpcspe/t-ppccomm"
>> ;;
>> powerpc-*-rtems*)
>> - tm_file="${tm_file} dbxelf.h elfos.h freebsd-spec.h newlib-stdint.h rs6000/sysv4.h rs6000/eabi.h rs6000/rtems.h rtems.h"
>> + tm_file="rs6000/biarch64.h ${tm_file} dbxelf.h elfos.h freebsd-spec.h newlib-stdint.h rs6000/sysv4.h rs6000/rtems.h rtems.h"
> This deletes eabi.h and I don't see you add all its definitions to
> rtems.h directly (NAME__MAIN etc.) Is this on purpose?
Yes, I always wondered why GCC added the __eabi() call to main() out of
thin air. In general, there is no main() function in RTEMS. Instead, you
can statically configure initialization threads. We call __eabi() in the
low-level startup code, e.g.
https://git.rtems.org/rtems/tree/c/src/lib/libbsp/powerpc/qoriq/start/start.S#n144
--
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-07-27 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 12:25 Sebastian Huber
2017-07-26 17:56 ` Segher Boessenkool
2017-07-27 5:28 ` Sebastian Huber [this message]
2017-07-27 19:57 ` Segher Boessenkool
2017-07-28 8:29 ` Sebastian Huber
2017-07-28 17:37 ` Segher Boessenkool
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=4518ab10-1391-5d3b-4b7e-af1e502d0919@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@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).