public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BIOS EMULATOR driver
Date: Tue, 27 Mar 2012 19:28:05 +0200	[thread overview]
Message-ID: <20120327172805.D5DCC2002FF@gemini.denx.de> (raw)
In-Reply-To: <CAJxx_aysp3cO1CasSNgycqE_yDNiBcMRwJ7P6GGR6T-d9QbB-A@mail.gmail.com>

Dear =?ISO-8859-2?Q?Viktor_K=F8iv=E1k?=,

In message <CAJxx_aysp3cO1CasSNgycqE_yDNiBcMRwJ7P6GGR6T-d9QbB-A@mail.gmail.com> you wrote:
>
> >> And even if it was, the combination of -ffunction-sections /
> >> -fdata-sections with --gc-sections should prevent any damages.
...
> Yes that's the main problem. Lots of code i unused. Basically
> everything except BootVideoCardBIOS, that is use in ATI video driver.
> I've got two solution of this problem. First, mark all unused code by
> some macro and compile it only conditionally or remove it. But I not
> sure if someone use this death code for debug purposes.

Did you check if you really find any such code in your linked image?
As I already explained, normally -ffunction-sections / -fdata-sections
with --gc-sections should make sure any unused functions get dropped
automatically.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I don't mind criticism. You know me. I've  never  been  one  to  take
offence  at  criticism. No one could say I'm the sort to take offence
at criticism -- Not twice, anyway. Not without blowing bubbles.
                                  - Terry Pratchett, _Witches Abroad_

  reply	other threads:[~2012-03-27 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 17:23 [U-Boot] BIOS EMULATOR driver Viktor Křivák
2012-03-25 18:30 ` Wolfgang Denk
2012-03-25 23:09   ` Viktor Křivák
2012-03-26  5:51     ` Wolfgang Denk
2012-03-26 10:43       ` Marek Vasut
2012-03-26 13:08         ` Wolfgang Denk
2012-03-26 13:31           ` Marek Vasut
2012-03-26 20:14             ` Wolfgang Denk
2012-03-26 23:06               ` Marek Vasut
2012-03-27  5:18                 ` Viktor Křivák
2012-03-27 17:28                   ` Wolfgang Denk [this message]
2012-03-27 17:48                     ` Marek Vasut
2012-03-27 17:51                       ` Timur Tabi
2012-03-27 17:58                         ` Marek Vasut
2012-03-27 17:59                           ` Timur Tabi
2012-03-27 20:11                             ` Marek Vasut
2012-03-27 22:46                               ` Viktor Křivák
2012-03-27 22:56                                 ` Graeme Russ
2012-03-27 23:46                                   ` Marek Vasut
2012-03-27 23:51                                     ` Graeme Russ
2012-03-27 23:56                                       ` Marek Vasut
2012-03-28  0:00                                         ` Graeme Russ
2012-03-28  0:17                                           ` Marek Vasut
2012-03-26 13:47           ` Viktor Křivák
2012-03-26 14:10             ` Anatolij Gustschin
2012-03-26 14:42             ` Timur Tabi
2012-03-26 20:17               ` Wolfgang Denk

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=20120327172805.D5DCC2002FF@gemini.denx.de \
    --to=wd@denx.de \
    --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