Message ID | 20100830003754.GA27228@intel.com |
---|---|
State | New |
Headers | show |
On 8/30/10 4:37 AM, H.J. Lu wrote: > Hi, > > Is there a reason to use | instead of || in TARGET_HAS_SINCOS? It's a typo. > This > patch replaces | with ||. OK for trunk? IMO, you can check it in under an obvious/typo rule. Thanks,
On Mon, Aug 30, 2010 at 12:24 AM, Maxim Kuvyrkov <maxim@codesourcery.com> wrote: > On 8/30/10 4:37 AM, H.J. Lu wrote: >> >> Hi, >> >> Is there a reason to use | instead of || in TARGET_HAS_SINCOS? > > It's a typo. > >> This >> patch replaces | with ||. OK for trunk? > > IMO, you can check it in under an obvious/typo rule. > I checked it in. Thanks.
diff --git a/gcc/config/linux.h b/gcc/config/linux.h index e283a9a..7c0ca95 100644 --- a/gcc/config/linux.h +++ b/gcc/config/linux.h @@ -160,6 +160,6 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see #define TARGET_C99_FUNCTIONS (OPTION_GLIBC) /* Whether we have sincos that follows the GNU extension. */ -#define TARGET_HAS_SINCOS (OPTION_GLIBC | OPTION_BIONIC) +#define TARGET_HAS_SINCOS (OPTION_GLIBC || OPTION_BIONIC) #define TARGET_POSIX_IO