From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] remove target_os
Date: Tue, 27 Jan 2009 22:52:59 +0100 [thread overview]
Message-ID: <1233093179.6503.5.camel@localhost> (raw)
In-Reply-To: <497F670B.6080902@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
El mar, 27-01-2009 a las 20:56 +0100, Christian Franke escribió:
> Javier Martín wrote:
> > El mar, 27-01-2009 a las 18:21 +0100, Christian Franke escribió:
> >
> >> Javier Martín wrote:
> >>
> >>>> Unfortunately, gcc has no '-fno_os' option to specify the bare CPU as
> >>>> target.
> >>>>
> >>>>
> >>> Might -ffreestanding be what you are looking for?
> >>>
> >>>
> >>>
> >> The option '-ffreestanding' is the same as '-fno-hosted'.
> >>
> >> According to gcc (4.3.1) source, '-fno-hosted' clears variable
> >> 'flag_hosted' and sets '-fno-builtin'. The latter is already set within
> >> GRUB build.
> >>
> >> A cleared 'flag_hosted' apparently has only 2 effects:
> >> - disable the special handling of 'main()'.
> >> - #define __STDC_HOSTED__ to 0 instead of 1
> >>
> >> There is no effect on the target_os dependent parts of the gcc code
> >> generation. For example, on i386, __enable_execute_stack() calls are
> >> generated for target_os netbsd, openbsd and cygwin, but not for linux.
> >> The emit call is hard-coded in
> >> gcc/configs/i386/i386.c:x86_initialize_trampoline().
> >>
> >
> > In that case, we are dealing with a GCC bug. We might want to require
> > the user to create a bare "no-OS" cross compiler.
> >
> >
>
> 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.
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2009-01-27 21:52 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 [this message]
2009-01-29 7:00 ` Christian Franke
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=1233093179.6503.5.camel@localhost \
--to=lordhabbit@gmail.com \
--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.