All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GCC 4.5
Date: Thu, 20 May 2010 10:53:37 -0500	[thread overview]
Message-ID: <4BF55B01.7010707@gmail.com> (raw)
In-Reply-To: <4BF5345A.5010103@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. I've noticed that GCC 4.5 is released and is available in
> debian. With this version -mregparam=3 bug is fixed. So I intend to
> remove all NESTED_FUNC_ATTR and use -mregparm=3 only on gcc >=4.5 and
> -mregparam=1 otherwise. This has the disadvatantage of increasing binary
> size with pre-4.5 gcc but it also greatly reduces the bug surface and so
> will eventually result in better quality. Any oppositions?
> I do not intend to require gcc 4.5, only highly recommend it.

There have been reports of problems with -Os in gcc-4.5.0.  In one case, 
the linux kernel is not functional. Specifically the file 
arch/x86/kernel/tsc.c causes a kernel panic.

I advise caution in this area.

   -- Bruce


      reply	other threads:[~2010-05-20 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 13:08 GCC 4.5 Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-20 15:53 ` Bruce Dubbs [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=4BF55B01.7010707@gmail.com \
    --to=bruce.dubbs@gmail.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.