From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] gcc (3.3.5) causing problems in our latest kernel.
Date: Mon, 4 Apr 2005 01:07:23 +0100 [thread overview]
Message-ID: <20050404000723.GD18349@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1112572589.5860.3.camel@mulgrave>
On Sun, Apr 03, 2005 at 06:56:28PM -0500, James Bottomley wrote:
> On Sun, 2005-04-03 at 23:13 +0100, Matthew Wilcox wrote:
> > Perhaps there's a difference between an inline function and a macro
> > in terms of constant propagation? If you turn __test_width() into
> > a macro, it should work (see the implementation of __get_user() in
> > asm-parisc/uaccess.h)
>
> Yes, if I change it to a pure #define, everything works OK.
>
> However, unless we can get the inline function to work, I still have to
> go back to davem ... Do I just tell him we can't fix our toolchain, so
> how about this?
Even if we can fix the toolchain, there's going to be a lot of people
out there who'd have to upgrade. I'd prefer it if we didn't have to
force an upgrade ...
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-04-04 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1112564457.5858.7.camel@mulgrave>
2005-04-03 22:13 ` [parisc-linux] gcc (3.3.5) causing problems in our latest kernel Matthew Wilcox
2005-04-03 23:56 ` James Bottomley
2005-04-04 0:07 ` Matthew Wilcox [this message]
2005-04-03 23:43 ` John David Anglin
2005-04-04 0:43 ` Randolph Chung
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=20050404000723.GD18349@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox