public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42954] [4.5 regression] TARGET_*_CPP_BUILDINS issues with gfortran
Date: Sun, 26 Sep 2010 16:47:00 -0000 [thread overview]
Message-ID: <20100926164700.l8gCAV0yoKJ71EATd4tcYQCYTk-WO5EYxvBjO5724_E@z> (raw)
In-Reply-To: <bug-42954-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42954
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.09.26 13:19:37
date| |
CC| |fxcoudert at gcc dot
| |gnu.org
AssignedTo|unassigned at gcc dot |fxcoudert at gcc dot
|gnu.org |gnu.org
Summary|gfortran with libcpp: |[4.5 regression]
|TARGET_*_CPP_BUILDINS |TARGET_*_CPP_BUILDINS
|issues (MinGW, FreeBSD, |issues with gfortran
|MIPS, Fry) |
Ever Confirmed|0 |1
--- Comment #6 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2010-09-26 13:19:37 UTC ---
(In reply to comment #5)
> Patch for fixing at least target part for preprocessor
Doesn't work, for example as config/alpha/linux.h uses c_dialect_cxx() in the
macro, which is not accessible from the Fortran front-end (being a C-family
function).
I'm conducting of full audit of these macros in config/, and will report back
here when it's done.
next parent reply other threads:[~2010-09-26 13:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42954-4@http.gcc.gnu.org/bugzilla/>
2010-09-26 16:47 ` fxcoudert at gcc dot gnu.org [this message]
2010-09-26 17:47 ` fxcoudert at gcc dot gnu.org
2010-09-27 10:31 ` [Bug fortran/42954] [4.5/4.6 " burnus at gcc dot gnu.org
2010-09-30 12:22 ` rguenth at gcc dot gnu.org
2010-09-30 21:19 ` nightstrike at gmail dot com
2010-10-03 12:02 ` fxcoudert at gcc dot gnu.org
2010-10-07 10:51 ` fxcoudert at gcc dot gnu.org
2010-11-07 17:07 ` burnus at gcc dot gnu.org
2010-11-08 9:30 ` burnus at gcc dot gnu.org
2011-01-05 16:50 ` pinskia at gcc dot gnu.org
2011-03-15 8:59 ` [Bug fortran/42954] [4.5/4.6/4.7 " fxcoudert at gcc dot gnu.org
2011-03-18 15:48 ` jb at gcc dot gnu.org
2011-03-25 20:01 ` jakub at gcc dot gnu.org
2011-06-27 16:12 ` jakub at gcc dot gnu.org
2011-10-26 17:21 ` jakub at gcc dot gnu.org
2011-10-27 2:01 ` [Bug fortran/42954] [4.5/4.6/4.7 regression] TARGET_*_CPP_BUILTINS " nightstrike at gmail dot com
2011-10-27 9:39 ` burnus at gcc dot gnu.org
2012-01-09 11:12 ` [Bug fortran/42954] [4.4/4.5/4.6/4.7 " burnus at gcc dot gnu.org
2012-06-22 2:07 ` [Bug fortran/42954] [4.5/4.6/4.7/4.8 " nightstrike at gmail dot com
2012-10-21 20:46 ` [Bug fortran/42954] [4.6/4.7/4.8 " janus at gcc dot gnu.org
2013-03-22 14:44 ` [Bug fortran/42954] [4.6/4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:58 ` [Bug fortran/42954] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-10-16 9:50 ` jakub at gcc dot gnu.org
2014-05-22 9:03 ` [Bug fortran/42954] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:41 ` [Bug fortran/42954] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:24 ` [Bug fortran/42954] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:16 ` [Bug fortran/42954] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:37 ` jakub at gcc dot gnu.org
2021-05-14 9:46 ` [Bug fortran/42954] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:04 ` rguenth at gcc dot gnu.org
2021-06-01 13:43 ` longb at cray dot com
2022-05-27 9:34 ` [Bug fortran/42954] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2022-12-19 14:36 ` pinskia at gcc dot gnu.org
2023-07-07 10:29 ` [Bug fortran/42954] [11/12/13/14 regression] TARGET_*_CPP_BUILTINS issues with gfortran / Target macros missing (C preprocessor) rguenth at gcc dot gnu.org
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=20100926164700.l8gCAV0yoKJ71EATd4tcYQCYTk-WO5EYxvBjO5724_E@z \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).