From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, gfortran List <fortran@gcc.gnu.org>
Subject: Re: [patch] Separate {OS,CPU}_CPP_BUILTINS macros into C-family and language-independent macros
Date: Fri, 08 Oct 2010 20:29:00 -0000 [thread overview]
Message-ID: <yddy6a8scl7.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4D88077B-3233-4D15-94E6-13BE58D29AD5@gmail.com> (FX's message of "Thu, 7 Oct 2010 12:49:34 +0200")
FX <fxcoudert@gmail.com> writes:
Please don't use application/octet-stream for patch attachments, this
makes it considerably harder to cite them.
2010-10-07 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
PR fortran/42954
* cppbuiltin.c (define_target_specific_builtins,
define_builtin_macro_std): New functions.
(define_language_independent_builtin_macros): Call
define_target_specific_builtins
Missing full stop?
(define_builtin_macros_for_type_sizes):
Something is weird here: what changed?
Index: gcc/config/alpha/osf5.h
===================================================================
--- gcc/config/alpha/osf5.h (revision 165065)
+++ gcc/config/alpha/osf5.h (working copy)
@@ -47,6 +47,7 @@ along with GCC; see the file COPYING3.
/* Names to predefine in the preprocessor for this target machine. */
+#undef TARGET_OS_CPP_BUILTINS
#define TARGET_OS_CPP_BUILTINS() \
do { \
builtin_define_std ("unix"); \
@@ -63,7 +64,11 @@ along with GCC; see the file COPYING3.
to be defined for <math.h>. */ \
if (LONG_DOUBLE_TYPE_SIZE == 128) \
builtin_define ("__X_FLOAT"); \
- \
+ } while (0)
+
+#undef TARGET_OS_CPP_BUILTINS_CFAMILY
+#define TARGET_OS_CPP_BUILTINS_CFAMILY() \
+ do { \
/* Tru64 UNIX V4/V5 provide several ISO C94 \
features protected by the corresponding \
__STDC_VERSION__ macro. libstdc++ v3 \
Why are you adding the #undef's? Do you really need them?
Index: gcc/doc/tm.texi
===================================================================
--- gcc/doc/tm.texi (revision 165065)
+++ gcc/doc/tm.texi (working copy)
Please avoid including generated files in the mail.
Index: gcc/doc/tm.texi.in
===================================================================
--- gcc/doc/tm.texi.in (revision 165065)
+++ gcc/doc/tm.texi.in (working copy)
@@ -672,7 +672,10 @@ the functions @code{builtin_define}, @co
@code{builtin_assert}. When the front end
calls this macro it provides a trailing semicolon, and since it has
finished command line option processing your code can use those
-results freely.
+results freely. This macro, however, will be used by all front-end using
^ two spaces ^s
Otherwise, the osf5.h, iris6.h and sol2.h changes are ok.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2010-10-08 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 10:49 FX
2010-10-07 11:14 ` Rainer Orth
2010-10-07 12:31 ` FX
2010-10-07 12:46 ` FX
2010-10-08 8:56 ` Tobias Burnus
2010-10-08 20:29 ` Rainer Orth [this message]
2010-10-16 19:44 ` Tobias Burnus
2010-10-20 22:34 ` FX
2010-11-03 21:29 FX
2010-11-03 22:34 ` Weddington, Eric
2010-11-03 22:35 ` FX
2010-11-04 17:05 ` Rainer Orth
2010-11-06 0:06 ` Jerry DeLisle
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=yddy6a8scl7.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).