From: Abdul Haleem <abdhalee@linux•vnet.ibm.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
linux-next <linux-next@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
Kees Cook <keescook@chromium•org>, mpe <mpe@ellerman•id.au>,
sachinp <sachinp@linux•vnet.ibm.com>
Subject: Re: [linux-next][bisected c7c133f3][gcc 4.8.5] build fail with error: first argument to ‘__builtin_choose_expr’ not a constant
Date: Wed, 14 Mar 2018 15:29:06 +0530 [thread overview]
Message-ID: <1521021546.31953.12.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <20180314193957.5f835d33@canb.auug.org.au>
On Wed, 2018-03-14 at 19:39 +1100, Stephen Rothwell wrote:
> Hi Abdul,
>
> On Wed, 14 Mar 2018 13:59:54 +0530 Abdul Haleem <abdhalee@linux•vnet.ibm.com> wrote:
> >
> > Today's next kernel fails to build with gcc 4.8.5 on powerpc machine.
>
> Thanks for the report. Just for the future, please include the
> next-XXXXXXXX tag when making reports about linux-next.
Sure, I will. next-20180313 is the bad tag
>
> > ./include/linux/jiffies.h: In function ‘jiffies_delta_to_clock_t’:
> > ./include/linux/kernel.h:855:2: error: first argument to ‘__builtin_choose_expr’ not a constant
> > __builtin_choose_expr(__builtin_constant_p(x) && \
> > ^
> > ./include/linux/kernel.h:867:19: note: in expansion of macro ‘__max’
> > #define max(x, y) __max(typeof(x), typeof(y), x, y)
> >
> > Machine Type: Power8 Baremetal
> > gcc: 4.8.5
> >
> >
> > Builds fine when below patch is reverted
> > c7c133f3 kernel.h: skip single-eval logic on literals in min()/max()
>
> Those patches have been removed from today's linux-next (next-20180314).
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
prev parent reply other threads:[~2018-03-14 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 8:29 [linux-next][bisected c7c133f3][gcc 4.8.5] build fail with error: first argument to ‘__builtin_choose_expr’ not a constant Abdul Haleem
2018-03-14 8:39 ` Stephen Rothwell
2018-03-14 9:59 ` Abdul Haleem [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=1521021546.31953.12.camel@abdul.in.ibm.com \
--to=abdhalee@linux$(echo .)vnet.ibm.com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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