From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] Eliminate NESTED_ATTR_FUNC
Date: Thu, 03 Sep 2009 17:49:49 +0200 [thread overview]
Message-ID: <1251992989.2870.8.camel@fz.local> (raw)
In-Reply-To: <20090903153623.GA18824@thorin>
Am Donnerstag, den 03.09.2009, 17:36 +0200 schrieb Robert Millan:
> On Wed, Sep 02, 2009 at 12:20:19PM +0800, Bean wrote:
> >
> > Hi,
> >
> > Oh, I was wrong previously, gcc does respect __attribute__
> > ((__regparm__ (3))) flag (I forget to add -Os so it still uses stack
> > to store value). And the bug is still there ! Try this test program:
>
> Thanks Bean. I have opened an entry in GCC bugzilla, and submitted your
> test program in it:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41246
>
> Hopefully they'll fix it in later versions, and hopefully people will
> upgrade soon. In the meantime, we're stuck with it.
>
Is there any reason why we fallback to regparm 1 and not to regparm 2?
According to the output of the testcase in the above bug report 2 seems
to work too?
--
Felix Zielcke
Proud Debian Maintainer
next prev parent reply other threads:[~2009-09-03 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 13:42 [RFC] Eliminate NESTED_ATTR_FUNC Vladimir 'phcoder' Serbinenko
2009-09-01 15:43 ` Bean
2009-09-01 16:02 ` Robert Millan
2009-09-01 16:05 ` Bean
2009-09-01 19:30 ` Yves Blusseau
2009-09-01 22:26 ` David Miller
2009-09-03 15:08 ` Vladimir 'phcoder' Serbinenko
2009-09-03 23:17 ` David Miller
[not found] ` <d7ead6de0909051404r50473aeao44aae7842a7d443b@mail.gmail.com>
[not found] ` <20090905.152320.164499705.davem@davemloft.net>
2009-09-06 17:12 ` Fwd: " Vladimir 'phcoder' Serbinenko
2009-09-08 14:43 ` Robert Millan
2009-09-02 4:20 ` Bean
2009-09-02 5:55 ` Yves Blusseau
2009-09-03 15:06 ` Vladimir 'phcoder' Serbinenko
[not found] ` <4A9FE6AD.9010509@gnu.org>
2009-09-03 16:52 ` Vladimir 'phcoder' Serbinenko
2009-09-03 15:36 ` Robert Millan
2009-09-03 15:49 ` Felix Zielcke [this message]
2009-09-03 15:59 ` Vladimir 'phcoder' Serbinenko
2009-09-03 16:01 ` Bean
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=1251992989.2870.8.camel@fz.local \
--to=fzielcke@z-51.de \
--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.