All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] disk: make get_partition_info() always available to disk.c
Date: Fri, 21 Sep 2012 16:18:11 -0600	[thread overview]
Message-ID: <505CE7A3.4080708@wwwdotorg.org> (raw)
In-Reply-To: <1348265104-1337-1-git-send-email-swarren@wwwdotorg.org>

On 09/21/2012 04:05 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
> 
> Now that get_device_and_partition() always calls get_partition_info()
> when disk.c is compiled, we must always compile the function, rather
> than ifdef it away.
> 
> Technically, this change is required before Rob's "disk/part: introduce
> get_device_and_partition" patch. However, at least when the compiler
> optimizer is turned on, it isn't required before then in practice,
> since get_device_and_partition() calls get_dev(), which is stubbed out
> in disk.c under exactly the same conditions that get_partition_info()
> is not compiled, and hence the compiler never generates code for the
> call to the missing function. However, in my later patch "disk:
> get_device_and_partition() "auto" partition and cleanup", the optimizer
> doesn't succeed at this, and may attempt to reference the undefined
> function.

Uggh. Even this isn't quite enough; e.g. CONFIG_DOS_PARTITION can be
enabled but not the defines that part_dos.c uses to ifdef out
compilation of get_partition_info_dos(). That seems illegal to me, but
anyway. I'll send another one once MAKEALL -a arm actually gets all the
way to the end...

      reply	other threads:[~2012-09-21 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 22:05 [U-Boot] [PATCH] disk: make get_partition_info() always available to disk.c Stephen Warren
2012-09-21 22:18 ` Stephen Warren [this message]

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=505CE7A3.4080708@wwwdotorg.org \
    --to=swarren@wwwdotorg.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 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.