From: Ron Flory <ron.flory@adtran.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: embedded gcc PPC toolchain questions
Date: Thu, 29 May 2003 13:56:16 -0500 [thread overview]
Message-ID: <3ED657D0.4070200@adtran.com> (raw)
In-Reply-To: 5.1.0.14.2.20030529125224.03782278@falcon.si.com
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. ;)
>
> References:
> http://sunsite.ualberta.ca/Documentation/Gnu/
> http://sunsite.ualberta.ca/Documentation/Gnu/gcc-3.0.2/html_node/gcc_100.html#SEC100
The refs are most useful. I was unaware that such low-level details of
gcc and friends had finally been documented, previous searches (a few years
ago) had turned up nada- or maybe i just didn't try hard enough...
thanks to all.
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.
ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-05-29 18:56 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 ` Ron Flory [this message]
2003-05-29 20:21 ` embedded gcc PPC toolchain questions Wolfgang Denk
[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=3ED657D0.4070200@adtran.com \
--to=ron.flory@adtran.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.