All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Warning fixes
Date: Wed, 6 Aug 2008 06:58:21 -0700	[thread overview]
Message-ID: <20080806065821.0dc2c6a0@gibibit.com> (raw)
In-Reply-To: <1218029942.27785.3.camel@ct>

On Wed, 06 Aug 2008 09:39:02 -0400
Pavel Roskin <proski@gnu.org> wrote:

> Hello!
> 
> I've fixed the trivial stuff, but this may require comments.  I'll be
> mostly offline for the next 3 weeks, so if it's OK, please apply it
> for me.

Along these lines, can we use a gcc option to turn off the "trampoline
requires executable stack" warnings that are generated by the dozens?
I looked for the option in the gcc manual and could not find it.

I think that the trampoline warning is the main thing left holding us
back from a warning-free build.  (IIRC there may be some
strict-aliasing warnings too... but those can be fixed by fixing the
code.)

Regards,
Colin



  reply	other threads:[~2008-08-06 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 13:39 [PATCH] Warning fixes Pavel Roskin
2008-08-06 13:58 ` Colin D Bennett [this message]
2008-08-06 14:32   ` Pavel Roskin
2008-08-06 15:08     ` Colin D Bennett
2008-08-13 10:18 ` Marco Gerards

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=20080806065821.0dc2c6a0@gibibit.com \
    --to=colin@gibibit.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.