From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch] rm9200 ethernet driver: board-specific quirk (csb337)
Date: Sat, 13 Jun 2009 10:19:01 -0700 [thread overview]
Message-ID: <200906131019.01529.david-b@pacbell.net> (raw)
In-Reply-To: <200906131113.51509.vapier@gentoo.org>
On Saturday 13 June 2009, Mike Frysinger wrote:
> > > > > See above. ?There already *IS* such an #ifdef, but it's just not
> > > > > cluttering up the guts of that driver.
> > > >
> > > > you adding MUST have NO size impact on other board
> > > >
> > > > if we apply you code as it we will increase the size of u-boot for
> > > > every rm9200 board that use the ethernet
Not on any compiler I've used for at least the past dozen years or so.
> > > i dont get it. ?the CPP expands into if(0) and unless you have a
> > > completely shitty compiler, gcc will do dead code elimination on it
> > > resulting in the same binary size.
> >
> > I've seen to much "shitty version" that does not do it correctly
> > so I prefer ot avoid the problem
Which compiler versions are that broken? And are used regularly
to build rm9200 U-Boot code? At normal optimization levels?
(We know that disabling optimization puts out all kinds of crap.)
This is really basic stuff: "if (0) { dead } else { live }" and
the converse.
> i'm pretty sure we're already relying on this behavior. ?so you've got a
> bigger problem that needs addressing (i.e. shit can that compiler) than what
> David is proposing.
I know that when Linux started relying on that type of dead-code
elimination quite a few years back, nobody thought this was a
real issue. And Linux is, on the whole, far more demanding of
compilers than U-Boot.
next prev parent reply other threads:[~2009-06-13 17:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 18:14 [U-Boot] [patch] rm9200 ethernet driver: board-specific quirk (csb337) David Brownell
2009-06-12 21:30 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-12 22:02 ` David Brownell
2009-06-13 10:26 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-13 11:13 ` David Brownell
2009-06-13 12:28 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-13 14:50 ` Mike Frysinger
2009-06-13 14:54 ` [U-Boot] [patch] rm9200 ethernet driver: board-specific quirk?(csb337) Jean-Christophe PLAGNIOL-VILLARD
2009-06-13 15:13 ` Mike Frysinger
2009-06-13 17:19 ` David Brownell [this message]
2009-07-10 20:39 ` Wolfgang Denk
2009-06-12 23:02 ` [U-Boot] [patch] rm9200 ethernet driver: board-specific quirk (csb337) Ben Warren
2009-06-18 5:14 ` Ben Warren
2009-06-19 6:59 ` David Brownell
2009-06-19 7:01 ` Ben Warren
2009-06-19 7:56 ` Jean-Christophe PLAGNIOL-VILLARD
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=200906131019.01529.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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