public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37821] [4.4 Regression] gfortran is ignoring #includes with the syntax <file.h>
Date: Mon, 03 Nov 2008 07:23:00 -0000 [thread overview]
Message-ID: <20081103072152.25480.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37821-16828@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from burnus at gcc dot gnu dot org 2008-11-03 07:21 -------
Subject: Bug 37821
Author: burnus
Date: Mon Nov 3 07:20:24 2008
New Revision: 141544
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141544
Log:
2008-11-03 Tobias Burnus <burnus@net-b.de>
PR fortran/37821
* cpp.c (gfc_cpp_add_include_path): Use BRACKET.
* scanner.c (add_path_to_list): Argument to add at head.
(gfc_add_include_path): Add new argument.
(gfc_add_intrinsic_modules_path) Update call.
(load_file): Print filename/line in the error message.
* gfortran.h (gfc_add_include_path): Update prototype.
* options.c (gfc_post_options,gfc_handle_module_path_options,
gfc_handle_option): Update call.
* lang-spec.h (F951_OPTIONS): Don't insert include path twice.
* arith.c (arith_error): Add -fno-range-error to the message.
2008-11-03 Tobias Burnus <burnus@net-b.de>
PR fortran/37821
* gfortran.dg/include_4.f90: New.
* gfortran.dg/include_5.f90: New.
* gfortran.dg/include_4.inc: New.
Added:
trunk/gcc/testsuite/gfortran.dg/include_4.f90
trunk/gcc/testsuite/gfortran.dg/include_4.inc
trunk/gcc/testsuite/gfortran.dg/include_5.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/arith.c
trunk/gcc/fortran/cpp.c
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/lang-specs.h
trunk/gcc/fortran/options.c
trunk/gcc/fortran/scanner.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37821
next prev parent reply other threads:[~2008-11-03 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 1:48 [Bug fortran/37821] New: " chris dot walter at duke dot edu
2008-10-14 1:51 ` [Bug fortran/37821] " chris dot walter at duke dot edu
2008-10-14 6:28 ` kargl at gcc dot gnu dot org
2008-10-14 12:12 ` [Bug fortran/37821] [4.4 Regression] " burnus at gcc dot gnu dot org
2008-10-14 12:24 ` dfranke at gcc dot gnu dot org
2008-10-14 12:32 ` burnus at gcc dot gnu dot org
2008-10-14 13:41 ` chris dot walter at duke dot edu
2008-10-15 9:30 ` burnus at gcc dot gnu dot org
2008-11-01 11:41 ` rguenth at gcc dot gnu dot org
2008-11-03 7:23 ` burnus at gcc dot gnu dot org [this message]
2008-11-03 7:36 ` burnus at gcc dot gnu dot 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=20081103072152.25480.qmail@sourceware.org \
--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).