From: Andrew Morton <akpm@linux-foundation.org>
To: Roland McGrath <roland@redhat.com>
Cc: torvalds@linux-foundation.org, jakub@redhat.com,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 1/2] UNREACHABLE() macro
Date: Fri, 11 Sep 2009 13:45:28 -0700 [thread overview]
Message-ID: <20090911134528.cd1782d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090910020031.87DC68BF6E@magilla.sf.frob.com>
On Wed, 9 Sep 2009 19:00:31 -0700 (PDT)
Roland McGrath <roland@redhat.com> wrote:
> +/*
> + * __builtin_unreachable is available in GCC 4.5+ and
> + * also in Fedora/Red Hat GCC 4.4.1-10+.
> + */
> +#if (__GNUC_MINOR__ > 4 \
> + || (__GNUC_MINOR__ == 4 \
> + && defined __GNUC_RH_RELEASE__ \
> + && (__GNUC_PATCHLEVEL__ > 1 \
> + || (__GNUC_PATCHLEVEL__ == 1 \
> + && __GNUC_RH_RELEASE__ >= 10))))
> +#define UNREACHABLE() __builtin_unreachable()
> +#endif
That's a bit of a mouthful. Did you consider a runtime probe with
scripts/Kbuild.include's try-run, cc-option, etc?
next prev parent reply other threads:[~2009-09-11 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 1:59 [PATCH 0/2] __builtin_unreachable Roland McGrath
2009-09-10 2:00 ` [PATCH 1/2] UNREACHABLE() macro Roland McGrath
2009-09-11 20:45 ` Andrew Morton [this message]
2009-09-11 20:59 ` Kyle McMartin
2009-09-11 21:55 ` Roland McGrath
2009-09-12 3:49 ` Arjan van de Ven
2009-09-12 4:43 ` H. Peter Anvin
2009-09-12 5:30 ` Arjan van de Ven
2009-09-12 5:52 ` Andrew Morton
2009-09-12 6:38 ` Jakub Jelinek
2009-09-13 20:10 ` H. Peter Anvin
2009-09-10 2:01 ` [PATCH 2/2] x86: BUG(): use UNREACHABLE() Roland McGrath
2009-09-10 4:42 ` [PATCH 0/2] __builtin_unreachable Américo Wang
2009-09-10 6:42 ` H. Peter Anvin
2009-09-10 6:13 ` Jakub Jelinek
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=20090911134528.cd1782d9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jakub@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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.