From: Gary Thomas <gary@mlbassoc.com>
To: Sergei Gavrikov <w3sg@SoftHome.net>
Cc: eCos patches list <ecos-patches@ecos.sourceware.org>
Subject: Re: Pedantic preprocessor
Date: Mon, 15 Oct 2007 11:29:00 -0000 [thread overview]
Message-ID: <47134EFE.9070602@mlbassoc.com> (raw)
In-Reply-To: <20071013214906.GA9874@ubuntu>
Sergei Gavrikov wrote:
> Hello list
>
> They spoke what 'untested' GCC3.4.1 (arm-elf) generates more compact
> code for float and double math than 'stable' GCC3.2.1 from ecoscentric
> ftp. I use 'stable' GCC3.2.1 and build 'new' toolchain to test that.
> That is (new code is a bit compact :). But, suddenly I found that the
> GCC3.4.1 preprocessor is more pedantic then GCC3.2.1 one. I wonder
> about CPP pedantism from other GCC suites (GCC3.4.X and GCC4.X.X). If a
> described issue the below is the GCC's 3.4.1, please, forget this. If
> other modern CPP cryes by a same way, a patch is attached.
>
> SYNOPSIS
>
> ecosconfig new sam7ex256
> ecosconfig tree
> make -s
> U CYGHWR_HAL_ARM_AT91, new inferred value AT91SAM7S
> U CYGHWR_HAL_ARM_AT91_FIQ, new inferred value 1
> U CYGHWR_HAL_ARM_AT91SAM7, new inferred value at91sam7x256
> headers finished
> cc1: warning: command line option "-Woverloaded-virtual" is valid for C++/ObjC++ but not for C
> cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for C
> cc1: warning: command line option "-Woverloaded-virtual" is valid for C++/ObjC++ but not for C
> cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for C
> cc1: warning: command line option "-Woverloaded-virtual" is valid for C++/ObjC++ but not for C
> cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for C
> build finished
>
> MEDICINE
>
> hal_arm.cdl describes 3 make rules to build arm.inc, vectors.o and
> target.ld. CPP 'sees' all $(CFLAGS) options and cryes about the
> language specific flags. I found that it's enough to replace $(CFLASG)
> by $(ACTUAL_CFLAGS), and all backs as it was with CPP from GCC3.2.1:
>
> headers finished
> build finished
>
> I like to see these 2 lines together. And if anybody knows how to fix
> this issue in platform CDL, please, enlight me.
>
Your patch is the correct one - I've applied it. Next time, don't
forget the ChangeLog entry.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2007-10-15 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 21:49 Sergei Gavrikov
2007-10-15 11:29 ` Gary Thomas [this message]
2007-10-16 9:18 ` Sergei Organov
2007-10-16 20:59 ` Sergei Gavrikov
2007-10-17 10:58 ` Sergei Organov
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=47134EFE.9070602@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=w3sg@SoftHome.net \
/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).