LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>,
Mike Travis <travis@sgi.com>
Subject: Re: linux-next: build failure
Date: Tue, 29 Jul 2008 10:00:55 +0200 [thread overview]
Message-ID: <20080729080055.GA28916@elte.hu> (raw)
In-Reply-To: <20080729162300.733b3e09.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Dave,
>
> Today's linux-next build (sparc64 defconfig) failed like this:
>
> kernel/time/tick-common.c: In function `tick_check_new_device':
> kernel/time/tick-common.c:210: error: invalid lvalue in unary `&'
> kernel/time/tick-common.c:223: error: invalid lvalue in unary `&'
> kernel/time/tick-common.c:255: error: invalid lvalue in unary `&'
>
> gcc is version 3.4.5 sparc64 cross compiler (powercp64 host).
>
> The below patch fixes it.
>
> when you take the address of the result. Noticed on a sparc64 compile
> using a version 3.4.5 cross compiler.
>
> kernel/time/tick-common.c: In function `tick_check_new_device':
> kernel/time/tick-common.c:210: error: invalid lvalue in unary `&'
> kernel/time/tick-common.c:223: error: invalid lvalue in unary `&'
> kernel/time/tick-common.c:255: error: invalid lvalue in unary `&'
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> include/linux/cpumask.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
> index 96d0509..d3219d7 100644
> --- a/include/linux/cpumask.h
> +++ b/include/linux/cpumask.h
> @@ -287,7 +287,7 @@ static inline const cpumask_t *get_cpu_mask(unsigned int cpu)
> * gcc optimizes it out (it's a constant) and there's no huge stack
> * variable created:
> */
> -#define cpumask_of_cpu(cpu) ({ *get_cpu_mask(cpu); })
> +#define cpumask_of_cpu(cpu) (*get_cpu_mask(cpu))
hm, i'm wondering - is this a compiler bug?
Ingo
next prev parent reply other threads:[~2008-07-29 8:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 6:23 linux-next: build failure Stephen Rothwell
2008-07-29 8:00 ` Ingo Molnar [this message]
2008-07-29 8:03 ` Stephen Rothwell
2008-07-29 8:58 ` Ingo Molnar
2008-07-29 11:28 ` KOSAKI Motohiro
2008-07-29 11:40 ` Ingo Molnar
2008-07-29 14:31 ` Mike Travis
2008-07-29 14:33 ` Mike Travis
2008-07-29 16:33 ` Linus Torvalds
2008-07-29 16:42 ` Ingo Molnar
2008-07-29 16:44 ` Linus Torvalds
2008-07-29 8:14 ` Wenji Huang
2008-07-29 16:26 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2013-11-08 16:51 linux-next " Mark Salter
2013-10-30 15:27 Mark Salter
2013-10-30 20:37 ` Stephen Rothwell
2013-10-30 20:50 ` Andrew Morton
2013-10-30 23:17 ` Stephen Rothwell
2008-10-20 12:04 linux-next: " Stephen Rothwell
2008-10-20 15:48 ` Greg KH
2008-10-20 16:33 ` J.R. Mauro
2008-10-20 16:51 ` Greg KH
2008-10-20 20:47 ` Greg KH
2008-10-20 22:34 ` J.R. Mauro
2008-10-20 22:31 ` Stephen Rothwell
2008-08-25 11:28 Stephen Rothwell
2008-08-25 12:40 ` Ingo Molnar
2008-08-28 7:40 ` David Miller
2008-07-28 5:07 Stephen Rothwell
2008-07-28 4:44 Stephen Rothwell
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=20080729080055.GA28916@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).