public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] uboot on microblaze, compilation error
Date: Sun, 21 Mar 2010 18:20:45 -0400	[thread overview]
Message-ID: <201003211820.51966.vapier@gentoo.org> (raw)
In-Reply-To: <20100321200029.2259E4C022@gemini.denx.de>

On Sunday 21 March 2010 16:00:29 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > i dont think the toolchain is broken.  this is standard gcc behavior for
> > all arches. ...
> 
> You are wrong here. It _is_ a bug of the toolchain if it auto-defines
> random unreserved identifiers.  This is NOT standard GCC behaviour.

they arent random, it's the arch-specific identifier.  and most arches do 
exactly that with gcc.  try actually looking at the builtins provided by x86, 
mips, and powerpc to mention just a few.
-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/20100321/9db016b0/attachment.pgp 

  reply	other threads:[~2010-03-21 22:20 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 [this message]
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
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=201003211820.51966.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