From: Marco Trudel <mtrudel@gmx.ch>
To: "Carlos O'Donell" <carlos@codesourcery.com>
Cc: gcc-help@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Making double precision constants work with -fsingle-precision-constant [was: Re: current subversion (rev 115032) compiling issues]
Date: Fri, 30 Jun 2006 19:27:00 -0000 [thread overview]
Message-ID: <44A57B14.20608@gmx.ch> (raw)
In-Reply-To: <20060628162557.GE2179@lios>
Problem solved by updating the gcc I use to build the current subversion
version to 4.2.0.
regards
Marco
Carlos O'Donell wrote:
> On Wed, Jun 28, 2006 at 11:02:00AM +0200, Marco Trudel wrote:
>> Your patch http://gcc.gnu.org/ml/gcc-patches/2005-12/msg00790.html seems
>> to break cross-compiling for windows, see attached forwarded message.
>
>>> Ok, next Problem:
>>> $GCC_BUILD_DIR/i686-pc-mingw32/libstdc++-v3/include/limits:1011: error:
>>> '__FLT_HAS_DENORM__' was not declared in this scope
>>> $GCC_BUILD_DIR/i686-pc-mingw32/libstdc++-v3/include/limits:1068: error:
>>> '__DBL_HAS_DENORM__' was not declared in this scope
>>> $GCC_BUILD_DIR/i686-pc-mingw32/libstdc++-v3/include/limits:1125: error:
>>> '__LDBL_HAS_DENORM__' was not declared in this scope
>>>
>>> Here I'm stuck because I'm unable to find the defining header or source
>>> file for these constants... Any ideas?
>
> The values of these definitions are computed by the compiler in gcc/c-cppbuiltins.c
> (c_cpp_builtins).
>
> Can you provide preprocessed source without macro expansion? I'm curious
> why a Windows hosted toolchain doesn't call c_cpp_builtins.
>
> Cheers,
> Carlos.
prev parent reply other threads:[~2006-06-30 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 9:19 current subversion (rev 115032) compiling issues Marco Trudel
2006-06-28 9:02 ` [PATCH] Making double precision constants work with -fsingle-precision-constant [was: Re: current subversion (rev 115032) compiling issues] Marco Trudel
2006-06-28 16:27 ` Carlos O'Donell
2006-06-30 19:27 ` Marco Trudel [this message]
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=44A57B14.20608@gmx.ch \
--to=mtrudel@gmx.ch \
--cc=carlos@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc-patches@gcc.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 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).