linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Ron Flory <ron.flory@adtran.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: embedded gcc PPC toolchain questions
Date: Thu, 29 May 2003 22:21:19 +0200	[thread overview]
Message-ID: <20030529202124.C010EC5492@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 29 May 2003 13:56:16 CDT." <3ED657D0.4070200@adtran.com>


In message <3ED657D0.4070200@adtran.com> you wrote:
>
> Jerry Van Baren wrote:
> > As a piece of very important trivia, note that Wolfgang's example
> > initialized the variable in the declaration.  If you don't initialize the
> > variable, it won't end up in the desired section.  Yes, that is in the gcc
> > manuals, just easy to miss :-).
>
>   Thanks- I've been surprised by this cute little 'feature' on other
> compilers.  Discovering it the hard way was a 'fun' way to blow a
> day or two.  ;)

Actually it should be no big surprise. I  think  every  (?)  standard
conforming  C  compiler  will  put  uninitialized  data  into the BSS
segment (usually .bss in the linker scripts).

> P.S.  Looking through past postings, are gcc 2.95.3 and binutils-2.10.1
>        still the recommended versions for embedded use?  Has confidence
>        in more modern versions been established yet?  I'll choose
>        reliability over optimization every time, but i've heard of subtle
>        issues with 2.95.3 as well.

We used 2.95.3 a long time for the ELDK, now we use 2.95.4.

No problems were reported (yet).

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There's no sense in being precise  when  you  don't  even  know  what
you're talking about.                             -- John von Neumann

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-05-29 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.2.20030529125224.03782278@falcon.si.com>
2003-05-29 18:56 ` embedded gcc PPC toolchain questions Ron Flory
2003-05-29 20:21   ` Wolfgang Denk [this message]
     [not found] <F0B628F30F48064289D8CCC1EE21B7A80C4884@mvebe001.americas.nokia.com>
2003-05-30  7:41 ` Wolfgang Denk
2000-10-19 22:47 linux-embedded: smallest kernel for 2.4.0-test9 Brendan J Simon
2000-10-20  2:07 ` Dan Malek
2003-05-29 15:38   ` embedded gcc PPC toolchain questions Ron Flory
2003-05-29 16:22     ` Wolfgang Denk
2003-06-02  6:26       ` Erik Christiansen

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=20030529202124.C010EC5492@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ron.flory@adtran.com \
    /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 NNTP newsgroup(s).