From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] uboot on microblaze, compilation error
Date: Mon, 22 Mar 2010 17:29:06 -0400 [thread overview]
Message-ID: <201003221729.07522.vapier@gentoo.org> (raw)
In-Reply-To: <20100322111852.69C3E4C022@gemini.denx.de>
On Monday 22 March 2010 07:18:52 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > So if a C compiler auto-defines something as "arm", or "i386", or
> > > "microblaze", then it is NOT standard-conforming - bare with me if I
> > > simply call this broken.
> >
> > that may be, but if that is what the gcc maintainer has decided, then
> > complaining about it wont fix code like u-boot. after all, u-boot hasnt
> > told
>
> Complaining about it might help to accelerate fixes which are already
> in the works. GCC documentation reads:
>
> We are slowly phasing out all predefined macros which are
> outside the reserved namespace. You should never use them in
> new programs, and we encourage you to correct older code to
> use the parallel macros whenever you find it.
>
> Complaining might make the "slowwly" a little faster. Not complaining
> certainly does not help at all.
perhaps, but it doesnt make projects compile any better, and i'd be suspicious
of how long it's actually going to take for that to become a reality. gcc has
behaved this way for years, and i dont see any sign of it changing (it hasnt
even started issuing warnings).
> > gcc that it wants strict preprocessor behavior (i.e. using something like
> > - ansi). if it did, then gcc wouldnt have output any non-prefixed
> > defines.
>
> Maybe we should do that?
looks like we already do, and you added it for precisely this reason (Aug
2009). i guess the OP is using an older version of u-boot which is why it's
still a problem for him ?
kind of makes this whole thread pointless noise ... sorry about that
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100322/4bfdffdf/attachment.pgp
next prev parent reply other threads:[~2010-03-22 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 18:36 [U-Boot] uboot on microblaze, compilation error Horst Gall
2010-03-17 19:16 ` Wolfgang Denk
2010-03-17 23:08 ` Mike Frysinger
2010-03-18 9:29 ` Michal Simek
2010-03-19 1:11 ` Mike Frysinger
2010-03-19 7:21 ` Michal Simek
2010-03-19 16:59 ` Mike Frysinger
2010-03-21 20:00 ` Wolfgang Denk
2010-03-21 22:20 ` Mike Frysinger
2010-03-21 22:45 ` Wolfgang Denk
2010-03-22 6:54 ` Mike Frysinger
2010-03-22 11:18 ` Wolfgang Denk
2010-03-22 21:29 ` Mike Frysinger [this message]
2010-03-22 21:39 ` Wolfgang Denk
2010-03-22 21:53 ` Mike Frysinger
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=201003221729.07522.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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