public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55534] -Wno-missing-include-dirs does not work with gfortran
Date: Mon, 29 Dec 2014 20:00:00 -0000	[thread overview]
Message-ID: <bug-55534-4-c7ne9szhIb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55534-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55534

--- Comment #9 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Manuel López-Ibáñez from comment #8)
> (In reply to Manuel López-Ibáñez from comment #7)
> > The ideal fix for this would adding a function like:
> 
> I forgot about this bug and redid the above from scratch. But this time, I
> actually tested that it works:
> https://gcc.gnu.org/ml/fortran/2014-10/msg00019.html

Has this patch been applied?

I checked r219084.  The bug is still there:

% gfc-trunk -Wno-missing-include-dirs xxx.f90 -I /no/such/dir
f951: Warning: Nonexistent include directory '/no/such/dir'
[-Wmissing-include-dirs]

At least I now see the colors...
>From gcc-bugs-return-471900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 29 20:32:12 2014
Return-Path: <gcc-bugs-return-471900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7822 invoked by alias); 29 Dec 2014 20:32:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7772 invoked by uid 48); 29 Dec 2014 20:32:07 -0000
From: "iverbin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64412] [regression] ICE in offload compiler: in extract_insn, at recog.c:2327
Date: Mon, 29 Dec 2014 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iverbin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64412-4-IcncXEb9y8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg02907.txt.bz2
Content-length: 362

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd412

--- Comment #9 from iverbin at gcc dot gnu.org ---
(In reply to H.J. Lu from comment #8)
> Created attachment 34357 [details]
> A patch
>
> Can you try this?

Thank you, e.53.5.c now passed.

However for-3.c and for-11.C still fails with another unrecognizable insn. I
attached reduced testcase (pr64412_2).


  parent reply	other threads:[~2014-12-29 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 20:31 [Bug fortran/55534] New: " anlauf at gmx dot de
2012-11-29 20:32 ` [Bug fortran/55534] " anlauf at gmx dot de
2012-12-04 23:02 ` anlauf at gmx dot de
2012-12-05  9:29 ` burnus at gcc dot gnu.org
2012-12-05 21:44 ` anlauf at gmx dot de
2012-12-06  0:04 ` burnus at gcc dot gnu.org
2012-12-07 21:10 ` anlauf at gmx dot de
2012-12-13 21:11 ` anlauf at gmx dot de
2014-09-09 21:39 ` manu at gcc dot gnu.org
2014-12-29 20:00 ` anlauf at gmx dot de [this message]
2014-12-29 21:28 ` manu at gcc dot gnu.org
2021-09-17  9:42 ` burnus at gcc dot gnu.org
2021-09-17 13:02 ` burnus at gcc dot gnu.org
2021-09-21  6:28 ` cvs-commit at gcc dot gnu.org
2021-09-21  7:13 ` burnus at gcc dot gnu.org
2021-09-22 18:58 ` cvs-commit at gcc dot gnu.org
2021-09-24  7:31 ` cvs-commit 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=bug-55534-4-c7ne9szhIb@http.gcc.gnu.org/bugzilla/ \
    --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).