This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix a couple of libstdc++ failures on uclinux

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Kazu Hirata <kazu at codesourcery dot com>
Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, richard at codesourcery dot com, joseph at codesourcery dot com
Date: Fri, 27 Apr 2007 12:58:26 +0200
Subject: Re: [patch] Fix a couple of libstdc++ failures on uclinux
References: <200704270019.l3R0J8QD018429@sparrowhawk.codesourcery.com>

+# Use the strongest available test out of AC_TRY_COMPILE and AC_TRY_LINK.
+AC_DEFUN([GCC_TRY_COMPILE_OR_LINK],
+[if test x$gcc_no_link = xyes; then
+  AC_TRY_COMPILE([$1], [$2], [$3], [$4])
+else
+  AC_TRY_LINK([$1], [$2], [$3], [$4])
+fi])

I like where you are going with this.

It seems like this could be used more consistently. Now we have

AC_TRY_LINK
AC_TRY_COMPILE

you are proposing:
AC_TRY_COMPILE_OR_LINK (via GCC_TRY_COMPILE_OR_LINK)

for a long time in libstdc++ we had:
AC_TRY_COMPILE_AND_LINK

The -fno-exceptions thing seems fine to me.

-benjamin

References:
- [patch] Fix a couple of libstdc++ failures on uclinux
  - From: Kazu Hirata

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]