All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Fix for grub_assert_fail undefined on NetBSD and other platforms
Date: Sat, 26 Dec 2009 14:28:00 +0100	[thread overview]
Message-ID: <20091226132800.GB20730@thorin> (raw)
In-Reply-To: <1261761718.3156.15.camel@fz.local>

On Fri, Dec 25, 2009 at 06:21:58PM +0100, Felix Zielcke wrote:
> Am Donnerstag, den 24.12.2009, 22:55 +0100 schrieb Robert Millan:
> > On Tue, Dec 22, 2009 at 09:39:07PM +0530, BVK Chaitanya wrote:
> > > Hi
> > > 
> > > 
> > > Attached is the patch, which removes use of undefined
> > grub_assert_fail
> > > function for catching bad-type-cast errors, with a better version
> > > __attribute__((error("msg"))) gcc extension.  With this extension,
> > gcc
> > > can give the exact location of the bad type cast at compile time.
> > 
> > Is this really a kind of error we'd like to report at run time?  Sorry
> > if
> > I'm missing something, but if we need additional code to handle it,
> > and it
> > was known at compile time, why do we do this?
> 
> __attribute__ ((error)) still reports it at compile time just like the
> old grub_assert_fail method.
> But the advantage is that you can specify the error message instead of
> just getting a `ld: unknown symbol grub_assert_fail' error during
> linking. And as BVK said above also the exact location where this
> happened.

Oh, ok.  Seems fine then.

-- 
Robert Millan

  "Be the change you want to see in the world" -- Gandhi



      reply	other threads:[~2009-12-26 13:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 16:09 Fix for grub_assert_fail undefined on NetBSD and other platforms BVK Chaitanya
2009-12-22 16:28 ` BVK Chaitanya
2009-12-22 17:07   ` Grégoire Sutre
2009-12-22 17:32     ` Felix Zielcke
2009-12-22 17:55     ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-23  6:01       ` BVK Chaitanya
2009-12-23 11:16         ` Gre'goire Sutre
2009-12-23 16:53           ` BVK Chaitanya
2009-12-24 21:55 ` Robert Millan
2009-12-25 17:21   ` Felix Zielcke
2009-12-26 13:28     ` Robert Millan [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=20091226132800.GB20730@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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.