From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] remove target_os
Date: Thu, 29 Jan 2009 08:00:40 +0100 [thread overview]
Message-ID: <49815418.7010302@t-online.de> (raw)
In-Reply-To: <1233093179.6503.5.camel@localhost>
Javier Martín wrote:
> El mar, 27-01-2009 a las 20:56 +0100, Christian Franke escribió:
>
>> Is building a bare 'no-OS' compiler supported by the upstream GCC sources?
>> Probably a too strict prerequisite for building GRUB.
>>
>
> I can't vouch so for all possible environments, but I can say that
> "clean" no-OS targets like i386-pc-elf exist at least for x86 and x86_64
> (this last being added as of GCC 4.3.2). However, as I said, if
> -ffreestanding does not do its job of providing a "true" freestanding
> environment (i.e. without relying on _any_ external libraries or
> syscalls, as opposite to the usual hosted environment), a bug report
> should be posted.
>
>
I haven't examined more recent gcc sources yet, the extra effect of
-ffreestanding on 4.3.1 is a no-op if the program does not use main().
How do those no-OS targets handle the platform independent libgcc
functions, e.g. __divdi3 which is used for 64bit integer division at
least on i386 ? Is a no-OS version of libgcc provided or should the
programmer handle these cases ?
Christian
next prev parent reply other threads:[~2009-01-29 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 23:12 [PATCH] remove target_os Robert Millan
2009-01-26 19:57 ` Christian Franke
2009-01-26 22:17 ` Javier Martín
2009-01-27 16:51 ` Vesa Jääskeläinen
2009-01-27 17:33 ` Javier Martín
2009-02-07 21:53 ` remove OS part of --target=xxx (Re: [PATCH] remove target_os) Robert Millan
2009-01-27 17:21 ` [PATCH] remove target_os Christian Franke
2009-01-27 17:40 ` Javier Martín
2009-01-27 19:56 ` Christian Franke
2009-01-27 21:52 ` Javier Martín
2009-01-29 7:00 ` Christian Franke [this message]
2009-02-07 21:54 ` Robert Millan
2009-02-08 19:59 ` Robert Millan
2009-02-07 21:48 ` Robert Millan
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=49815418.7010302@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.