From: FX <fxcoudert@gmail.com>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
Tobias Burnus <burnus@net-b.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [fortran, patch] IEEE intrinsic modules (ping)
Date: Mon, 07 Jul 2014 12:01:00 -0000 [thread overview]
Message-ID: <5A414AAE-5B7E-462A-83AD-517A723C16F2@gmail.com> (raw)
In-Reply-To: <CAO9iq9FzVpJhGRzAMif+7z5kNasFiYVQGm=hF7oQOiJckDh7Bg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
> Right, that's what I (vaguelly) remembered. Please consider a patch
> removing the ifndef __GNUC__ stuff from libgfortran.h pre-approved.
The only occurrence (outside of libcaf) is in libgfortran.h. Committed attached patch as rev. 212328, after building on x86_64-linux.
FX
[-- Attachment #2: x --]
[-- Type: application/octet-stream, Size: 1030 bytes --]
Index: libgfortran.h
===================================================================
--- libgfortran.h (revision 212327)
+++ libgfortran.h (working copy)
@@ -107,14 +107,8 @@ typedef off_t gfc_offset;
heuristic will mark this branch as much less likely as unlikely() would
do. */
-#ifndef __GNUC__
-#define __attribute__(x)
-#define likely(x) (x)
-#define unlikely(x) (x)
-#else
#define likely(x) __builtin_expect(!!(x), 1)
#define unlikely(x) __builtin_expect(!!(x), 0)
-#endif
/* Make sure we have ptrdiff_t. */
Index: ChangeLog
===================================================================
--- ChangeLog (revision 212327)
+++ ChangeLog (working copy)
@@ -1,5 +1,9 @@
2014-07-07 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
+ * libgfortran.h: Assume __GNUC__.
+
+2014-07-07 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
+
* runtime/stop.c: Use C11 _Noreturn.
* libgfortran.h: Use C11 _Noreturn in prototypes.
Move REALPART, IMAGPART and COMPLEX_ASSIGN macros...
next prev parent reply other threads:[~2014-07-07 12:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 9:30 [fortran, patch] IEEE intrinsic modules Uros Bizjak
2014-06-05 9:35 ` FX
2014-06-05 9:56 ` Uros Bizjak
2014-06-15 20:38 ` [fortran, patch] IEEE intrinsic modules (ping) FX
2014-06-23 8:40 ` FX
2014-06-23 19:23 ` Steve Kargl
2014-06-23 20:20 ` Steve Kargl
2014-06-24 8:11 ` FX
2014-06-24 16:49 ` Steve Kargl
2014-06-24 17:46 ` Steve Kargl
2014-06-24 18:34 ` Tobias Burnus
2014-06-24 19:19 ` Steve Kargl
2014-06-24 19:43 ` FX
2014-06-24 20:23 ` Steve Kargl
2014-06-24 20:26 ` FX
2014-06-24 20:37 ` Steve Kargl
[not found] ` <20140624205518.GA81619@troutmask.apl.washington.edu>
[not found] ` <852C0E47-A1AE-4D64-98B5-4338D2EE4CC2@gmail.com>
[not found] ` <20140624215016.GA81800@troutmask.apl.washington.edu>
2014-06-24 23:41 ` FX
2014-06-25 14:24 ` Steve Kargl
2014-06-29 8:43 ` Andreas Schwab
2014-06-29 9:53 ` FX
2019-02-28 19:22 ` Thomas Schwinge
2019-03-21 19:12 ` Thomas Schwinge
2014-07-05 20:42 ` Rainer Orth
2014-07-06 20:13 ` FX
2014-07-07 6:44 ` Janne Blomqvist
2014-07-07 8:29 ` FX
2014-07-07 9:10 ` Janne Blomqvist
2014-07-07 9:17 ` FX
2014-07-07 10:18 ` Janne Blomqvist
2014-07-07 12:01 ` FX [this message]
2014-07-07 8:30 ` Rainer Orth
2014-07-07 8:37 ` FX
2014-07-07 8:56 ` Rainer Orth
2014-07-07 9:00 ` FX
2014-07-07 9:03 ` Rainer Orth
2014-07-07 10:02 Tobias Burnus
2014-07-10 7:31 Uros Bizjak
2014-07-10 8:46 ` FX
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=5A414AAE-5B7E-462A-83AD-517A723C16F2@gmail.com \
--to=fxcoudert@gmail.com \
--cc=blomqvist.janne@gmail.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).